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

RIS box @ MAE-West
by Arife Vural 28 Sep '04

28 Sep '04

Hi Thomas, Joe, On RRC08, we could not get enough peers and that makes the route collector less functional. Because of that, we are thinking to relocate RRC08 at PAIX. We hope that would give us a chance to get more peers and better view there. Peter Losher will help us to move the box from MAE-West to PAIX. We are hoping to do those changes early September. I would like to thank you all your help for hosting RRC08 at MAE-West. Kind regards. Arife

4 28

http://www4.ripe.net/ris/
by Matthew Williams 01 Sep '04

01 Sep '04

Hi there, Did a little more work there. Pls check it out. We should probably plan one more meeting (dedicated afternoon?) for going through the final stuff. Cheers, Matthew

2 4

R: Kernel on RRC06
by Arife Vural 31 Aug '04

31 Aug '04

Hereby I wish to request a service from Operations. Detailed description: --------------------- MD5 support on RRC06 does not work and I'm just wondering whether we still use the kernel that Japan guy compiled. If this is the case, then MD5 might not be enabled on RRC06 properly. Few other things which are related with rrc rsync schema, I got this warning when I run ps command on RRCs, arife@rrc06:~$ ps aux |grep bgpd {sys_alarm} {register_sysctl_table} Warning: /System.map does not match kernel data. quagga 253 0.3 3.9 39948 36072 ? S Jun23 326:06 /usr/lib/quagga/bgpd --daemon arife 14412 0.0 0.0 1516 480 ttyp1 S 16:15 0:00 grep bgpd Anything to be worried or not? Also could you please change the owner of /etc/quagga dirs to quagga user and group? It's owned by root and when you make bgp config changes, it's not allowed to save the config. Regards, Arife Vural

1 0

bgpd dies
by James Aldridge 31 Aug '04

31 Aug '04

http://bugzilla.quagga.net/show_bug.cgi?id=103 We seem to be seeing this bug too. Don't know whether it's a Linux thing or a Quagga version 0.96.5 thing... worth keeping an eye on the quagga-users and quagga-dev lists. James

2 2

IPv6 updates plots
by James Aldridge 31 Aug '04

31 Aug '04

Take a look at http://www.ris.ripe.net/ipv6-updates/all/ (or any of the individual RRC's plots) and you'll see a certain periodicity about the graph. It seems that the RRD is only getting about half the data: 5 minutes and 35 minutes past each hour: weesp runs the "collect" script and pushes the raw files to halfweg. 0 minutes past each hour: halfweg runs the "ipv6-updates/update.sh" script looking for files from the "previous hour" (date -d "1 hour ago" +"%Y%m%d.%H"). However, at this time, only files up to the last run of "collect" (25 minutes earlier) are present - YYYYMMDD.HH00 to YYYYMMDD.HH35. Next time "update.sh" runs, an hour later, it again only looks at files from the previous hour (and not the missing files from the hour before that). Data from the last 25 minutes of each hour are never inserted into the RRD. A solution to this would be for risops@halfweg's crontab to run the "ipv6-updates/update.sh" sufficiently long after 5 minutes past the hour for the "collect" run on weesp to have pushed all the previous hour's files to halfweg. Thoughts? James

2 1

Tool to check RIS peering status
by James Aldridge 30 Aug '04

30 Aug '04

~risops/bin/peerstat is a simple script to report BGP peering status Examples: "peerstat all -lt 300" will show all peers which have changed state within 5 minutes (300 seconds) - typically peers which are flapping. risops@halfweg:~$ peerstat all -lt 300 AS20940 [ 195.66.224.168 ] on rrc01 DOWN for 0w 0d 0h 0m 4s (4 seconds) AS12222 [ 198.32.160.47 ] on rrc11 UP for 0w 0d 0h 0m 10s (10 seconds) "peerstat rrc00,rrc01 -gt 86400" will show all peers on rrc00 and rrc01 which have been down for more than 86400 seconds (1 day): risops@halfweg:~$ peerstat rrc00,rrc01 -gt 86400 AS3257 [ 195.69.144.85 ] on rrc00 down "for ever" AS15861 [ 195.66.224.40 ] on rrc01 down "for ever" AS5604 [ 195.66.224.41 ] on rrc01 down "for ever" AS1299 [ 195.66.224.48 ] on rrc01 down "for ever" AS12513 [ 195.66.224.117 ] on rrc01 down "for ever" AS15861 [ 195.66.226.40 ] on rrc01 down "for ever" AS8272 [ 195.66.226.47 ] on rrc01 down "for ever" AS2818 [ 195.66.226.103 ] on rrc01 DOWN for 5w 6d 19h 0m 0s (3610800 seconds) AS8210 [ 195.66.226.107 ] on rrc01 DOWN for 2w 3d 6h 0m 0s (1490400 seconds) AS12390 [ 195.66.226.119 ] on rrc01 down "for ever" AS13127 [ 195.66.226.142 ] on rrc01 DOWN for 2w 6d 11h 0m 0s (1767600 seconds) "peerstat rrc08 -gt 2419200" will show all peers on rrc08 which have been down for more than 2419200 seconds (4 weeks): risops@halfweg:~$ peerstat rrc08 -gt 2419200 AS2551 [ 198.32.200.14 ] on rrc08 down "for ever" James

1 0

Fw: NCC#2004081420 [RIPE beacon request!]
by RIS 30 Aug '04

30 Aug '04

Hi guys, What do you think about the following request? It looks he is asking to extend our anycast failover scenario to more RRCs. After discussing with him what kind of patterns he needs, we can use same prefix or we can use one of the free Beacon Prefixes. Arife ----- Begin forwarded message ----- Date: Fri, 13 Aug 2004 20:39:14 -0400 From: "Hitesh Ballani" <hitesh(a)cs.cornell.edu> To: <ris(a)ripe.net> Subject: NCC#2004081420 RIPE beacon request! Message-Id: <81224EA6DDA07C43BC7555E32401029E054219(a)EXCHVS2.cs.cornell.edu> Hello, I was wondering if you could spare a beacon for the following experiment: At the moment, one of your beacons (195.80.233.0/24) at advertised from 2 locations - LINX and AMS-IX. An interesting question is to study anycast fail-over time from an end user perspective - i.e given that the advertisement is withdrawn from AMS-IX at a particular instant, how long is it before convergence is reached and packets from a node, which were earlier being routed to AMS-IX, are routed to LINX. I tried running this experiment from a bunch of nodes on Planetlab but I have not been able to locate any node whose packets are routed to AMS-IX and so, I am never able to analyze the convergence time (for that matter, even nodes in Netherlands have their packets routed to LINX). Here, "packets being routed to LINX" implies that periodic traceroutes from my Planetlab sites show so. This is important to me as I am currently working an a proxy based deployment model for IP anycast and so anycast failover time through BGP is critical for me (see http://www.cs.cornell.edu/People/francis/pias.pdf and http://www.cs.cornell.edu/People/francis/pias/pias-worlds.pdf for details!). As a matter of fact we are in the process of obtaining 3 /22 blocks from ARIN for this very purpose - however, given the long drawn nature of that process, I thought it would be nice if I could use your advertisement infrastructure to answer some niggling questions which are critical for the success of our proposal. I was wondering if it would be possible for me to get a beacon to be advertised from more locations (ideally, from America(RRC08), Europe(a number of locations), and Asia(RRC06)). While a beacon being advertised from 2 locations would suffice for the above experiment, but advertisements from more than 2 locations would allow me to look at other stuff such as - How good is IP anycast at selecting nearby locations? Ideally, when a node sends out a packet to a anycast location, it should be routed to the destination which is closest - but with the policy based nature of BGP, it is not clear if it does. Such an experiment would make more sense with greater number of advertising locations. I tried determining answers to these questions using the anycasted root servers and the servers belonging to the AS-112 project but the hierarchical nature of their deployment prevents me from coming to any conclusions. While the above description may sound as if I am looking for just an end-user analysis, but I will also be looking at BGP updates for the anycast prefix to determine if advertising a prefix from many locations has an adverse impact on the visibility of the prefix due to reasons such as route flap dampening. If the above description sounds terribly confusing, I will be glad to provide additional details about the experiments I plan to run. Also, if such an arrangement is possible, I will plan out the detailed A/W pattern and the sites involved. Thanks, Hitesh ------ End forwarded message ------

4 4

RRC06
by Henk Uijterwaal (RIPE NCC) 27 Aug '04

27 Aug '04

Hi, Mainly FYI. I had an action on myself to contact Akiro Kato re: more peerings at the Japan RRC. He suggested a couple of mailing lists to write to. I did that yesterday, if you see a flurry of peering requests from there, blame me. If you don't, blame me as well ;-) 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

Fw: NCC#2004081626 [Re: Test allocations]
by RIPE NCC RIS 26 Aug '04

26 Aug '04

Hello RIS-all, As a request from RS, we stopped announcing the following prefixes through the RIS AS number on 18/08/2004: 85.192.0.0/16 85.255.248.0/21 But it appears that yesterday we restarted to announce the same prefixes. Can it be that some old configuration showed up again? What should be done to cancel these announcements? Vasco Asturiano ----- Begin forwarded message ----- Date: Thu, 26 Aug 2004 12:55:56 +0200 From: Mike Petuschak <mike(a)ripe.net> To: RIS <ris-request(a)ripe.net> Subject: Re: NCC#2004081626 Test allocations Cc: Pierre Baume <pierre(a)ripe.net>, Timothy Lowe <timothy(a)ripe.net> Message-Id: <20040826105556.GA30815(a)ripe.net> Hi, It looks like you started announcing the ranges from 85/8 once again, could you please remove them? > whois -h riswhois.ripe.net -M 85.192/10 % This is RIPE NCC's Routing Information Service % whois gateway to collected BGP Routing Tables % IPv4 or IPv6 address to origin prefix match % % For more information visit http://www.ripe.net/ris/riswhois.html route: 85.192.0.0/16 origin: AS12654 descr: RIPE-NCC-RIS-AS RIPE NCC RIS Project. lastupd-frst: 2004-08-17 09:00Z 195.69.144.234@rrc03 lastupd-last: 2004-08-24 21:37Z 80.81.192.126@rrc12 seen-at: rrc03,rrc04,rrc07,rrc12 num-rispeers: 7 source: RISWHOIS route: 85.255.248.0/21 origin: AS12654 descr: RIPE-NCC-RIS-AS RIPE NCC RIS Project. lastupd-frst: 2004-08-17 09:00Z 195.69.144.234@rrc03 lastupd-last: 2004-08-24 21:37Z 80.81.192.126@rrc12 seen-at: rrc03,rrc04,rrc07,rrc12 num-rispeers: 7 source: RISWHOIS -- Sincerely, Mike Petuschak RIPE NCC > Dear Arife, > > Please only remove the ranges from 85/8, i.e. > network 85.192.0.0/16 > network 85.255.248.0/21 > > the following route objects needs to be removed too: > > route: 85.192.0.0/16 > descr: RIPE-NCC-RIS New Allocation Filter Checking > origin: AS12654 > mnt-by: RIPE-NCC-RIS-MNT > changed: risops(a)ripe.net 20040402 > source: RIPE > > route: 85.255.248.0/21 > descr: RIPE-NCC-RIS New Allocation Filter Checking > origin: AS12654 > mnt-by: RIPE-NCC-RIS-MNT > changed: risops(a)ripe.net 20040402 > source: RIPE > > > > > >> It looks we are announcing the following networks, do you want >> me to remove all? >> >> network 85.192.0.0/16 >> network 85.255.248.0/21 >> network 86.192.0.0/16 >> network 86.255.248.0/21 >> network 87.192.0.0/16 >> network 87.255.248.0/21 >> network 88.192.0.0/16 >> network 88.255.248.0/21 >> >> Arife >> >> On Tue, 17 Aug 2004 09:41:13 +0200, Mike Petuschak wrote: >>> Dear RIS, >>> >>> As both James & Daniel are on holidays, >>> can somebody else please stop announcing the >>> ranges from 85/8 and remove the route objects? >>> >>> Thanks a lot. >>> >>> -- >>> Mike >>> >>> ----- Forwarded message from Mike Petuschak <mike(a)ripe.net> ----- >>> >>> Date: Tue, 10 Aug 2004 16:38:15 +0200 >>> From: Mike Petuschak <mike(a)ripe.net> >>> To: James Aldridge <james(a)ripe.net> >>> Cc: Daniel Karrenberg <dfk(a)ripe.net>, lsd(a)ripe.net, >>> Pierre Baume <pierre(a)ripe.net> >>> Subject: Re: Test allocations >>> >>> Dear James, >>> >>> Could you please stop announcing the ranges from 85/8 and remove the route >>> objects? We allocated first /12 from 85/8. ------ End forwarded message ------ --

1 0

RE: myASn in training
by Matthew Williams 25 Aug '04

25 Aug '04

> yes, i can! Excellent :) Cheers, Matthew > -----Original Message----- > From: Vesna Manojlovic [mailto:BECHA@ripe.net] > Sent: 25 August 2004 09:20 > To: Matthew Williams > Subject: Re: myASn in training > > > hi matthew, > > > On Tue, 24 Aug 2004 19:39:44 +0200 > "Matthew Williams" <matthew(a)ripe.net> wrote: > > > Hi Vesna, > > > > Do you now know whether you can join the meeting (see ctime)? > > > > yes, i can! > > > > I would like to know this before I go to Can next week. > > > > have a good time :) > > > Cheers, > > Matthew > > > thanks, > b >

1 0

RE: myASn in training
by Matthew Williams 24 Aug '04

24 Aug '04

Hi Vesna, Do you now know whether you can join the meeting (see ctime)? I would like to know this before I go to Can next week. Cheers, Matthew > -----Original Message----- > From: Matthew Williams [mailto:matthew@ripe.net] > Sent: 18 August 2004 19:44 > To: 'Vesna Manojlovic' > Cc: 'ris-int(a)ripe.net'; 'rumy(a)ripe.net'; 'arno(a)ripe.net' > Subject: RE: myASn in training > > > > > > > Hi Matthew, all, > > > > let's meet to talk about it :) Will you make the C-time entry? > > > > Will do. Who should be there? Arife, Arno, you and I? > > > On Tue, 17 Aug 2004 14:04:00 +0200 > > "Matthew Williams" <matthew(a)ripe.net> wrote: > > > > > [thanks for the hook-up, Rumy] > > > > > > Hi Vesna, > > > > > > Arife should be included on this too. > > > > > > > Vesna: could you discuss this with Matthew (and if necessary > > > > Arno and/or > > > > Ferenc) and let me know what your thoughts are? > > > > > > Include a section in rr training? > > > > > > > We already have one slide in the RR course about the myASn; > > sometimes we used to show the demo (but I think my account > > expired...). > > Nope, should be okay unless you're trying to access the old prototype. > > > > > We can maybe change that -- depending on how much attention > > you want to give to this service, and how much space we can > > "free-up" in the curent course, and how it fits with the rest > > of topics.. > > > > Personally, I would prefere if we can do some hands-on with > > the "myASn", but that would require opening 20 (or 5?) > > demo-accounts for each course, thinking of the tasks to give > > to the participants (or sub-groups), deciding what are the > > most useful features to let them see/practice, how much time > > it takes to do all that etc... > > > > I guess this brain-dump puts some of the topics on the agenda > > for the meeting :) > > Fine. > > Cheers, > Matthew > > > > > > Cheers, > > > Matthew > > > > > > > ciao, > > becha > > > > > > > > -----Original Message----- > > > > From: Rumy Kanis [mailto:rumy@ripe.net] > > > > Sent: 17 August 2004 13:55 > > > > To: Matthew Williams; 'Rumy Kanis'; becha(a)ripe.net > > > > Cc: 'Henk Uijterwaal'; 'Matthew Williams' > > > > Subject: myASn in training > > > > > > > > > > > > Hi Matthew, > > > > > > > > I am sort of getting back up to speed again :-) but still > > > > drowning in my mails. > > > > > > > > I am including Vesna in this reply, I think it would be best > > > > if you discuss > > > > this with her. Vesna has the overall responsibility over the > > > > different > > > > training courses and their content (Arno has > > responsibility over the > > > > advanced courses, Ferenc over the LIR). Vesna will have a good > > > > understanding of whether this fits into one of our trainings > > > > and if so, > > > > into which one and in what format. > > > > > > > > Vesna: could you discuss this with Matthew (and if necessary > > > > Arno and/or > > > > Ferenc) and let me know what your thoughts are? > > > > > > > > Thanks! > > > > > > > > Cheers, > > > > Rumy > > > > > > > > > > > > At 02:37 PM 7/29/2004 +0200, Matthew Williams wrote: > > > > >Hi Rumy, > > > > > > > > > >I see that you're on VAC until mid-Aug. Please get back > > to me when > > > > >you're > > > > >up to speed again. > > > > > > > > > >Hope hols were relaxing :) > > > > > > > > > >Cheers, > > > > >Matthew > > > > > > > > > > > -----Original Message----- > > > > > > From: Matthew Williams [mailto:matthew@ripe.net] > > > > > > Sent: 22 July 2004 18:02 > > > > > > To: 'Rumy Kanis' > > > > > > Cc: 'Henk Uijterwaal' > > > > > > Subject: FW: Announcement Routing Registry Training Courses > > > > > > > > > > > > > > > > > > Hi Rumy, > > > > > > > > > > > > Henk suggested that I get in touch with you about > > > > including a myASn > > > > > > section into one of your trainings. Version 1 will be > > > > ready before > > > > > > the next RIPE meeting. Any thoughts? ;) > > > > > > > > > > > > Cheers, > > > > > > Matthew > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: routing-wg-admin(a)ripe.net > > > > [mailto:routing-wg-admin@ripe.net] > > > > > > > On Behalf Of RIPE NCC Training > > > > > > > Sent: 21 July 2004 16:27 > > > > > > > To: local-ir(a)ripe.net; db-wg(a)ripe.net; > routing-wg(a)ripe.net; > > > > > > > irrtoolset(a)ripe.net > > > > > > > Subject: Announcement Routing Registry Training Courses > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dear Colleagues, > > > > > > > > > > > > > > [apologies for duplicate postings] > > > > > > > > > > > > > > As a service to its members the RIPE NCC offers > the "Routing > > > > > > > Registry Training Course". > > > > > > > > > > > > > > The main objective of the "Routing Registry Training > > > > Course" is to > > > > > > > familiarise the LIRs with the features of the Routing > > > > > > > Registry, > > > > > > > while introducing the relevant tools and services of > > > > the RIPE NCC. > > > > > > > The course also offers practical exercises. > > > > > > > > > > > > > > OVERVIEW OF TOPICS COVERED IN THE COURSE: > > > > > > > - Routing Registry as a part of the RIPE Whois > Database and > > > > > > > the > > > > > > > Internet Routing Registry (IRR) > > > > > > > - Specifying routing policies using (RPSL) > > > > > > > Routing Policy Specification Language and the > RtConfig tool > > > > > > > - IRRToolSet > > > > > > > - Routing Information Service (RIS) > > > > > > > - Routing Registry Consistency Check Project > > > > > > > > > > > > > > Please note that this is an advanced course. It will: > > > > > > > - NOT teach the basics of routing > > > > > > > - NOT teach the basics of RIPE Database operations, > > > > > > > - NOT describe how to receive Internet resources from > > > > the RIPE NCC > > > > > > > - NOT describe how to operate a Local Internet > > Registry (LIR) > > > > > > > > > > > > > > The target audience of the course are technical staff of > > > > > > > LIRs: e.g. network operators, engineers etc. This > course is > > > > > > > not > > > > > > > intended for administrative or management staff (e.g. > > > > > > > Hostmasters) . It is assumed that all attendees will be > > > > > > familiar with > > > > > > > Border Gateway Protocol routing and with the RIPE > > > > Database (i.e. > > > > > > > creating/modifying objects). > > > > > > > > > > > > > > This course is based on interactive exercises in a > > > > local network > > > > > > > set-up. Please bring your laptops equipped with the > > > > > > following: > > > > > > > - A working Ethernet card, > > > > > > > - Three meters of Ethernet cable, > > > > > > > - A secure connection client, > > > > > > > - A web browser. > > > > > > > > > > > > > > Please be prepared to share your laptop (or at least > > > > allow another > > > > > > > attendee to "look over your shoulder") if necessary. > > > > > > > > > > > > > > The Routing Registry Training Course is conducted in > > > > the English > > > > > > > language and is free of charge, since it is covered by the > > > > > > > membership fee. > > > > > > > > > > > > > > More information about the Routing Registry Training > > > > Course can be > > > > > > > found > > > > > > > at: http://www.ripe.net/training/rr/ > > > > > > > > > > > > > > REGISTRATION: > > > > > > > > > > > > > > You can register for a Routing Registry Training > > Course at the > > > > > > > following URL: > > http://www.ripe.net/cgi-bin/trainingform.pl.cgi > > > > > > > > > > > > > > Or by completing the registration form at the end of > > > > this e-mail > > > > > > > and replying to <training(a)ripe.net> . In order to > > > > register for a > > > > > > > Routing Registry Training Course you must be an > > > > employee of an LIR > > > > > > > and either: > > > > > > > - be an LIR contact > > > > > > > - be confirmed by an LIR contact > > > > > > > > > > > > > > LIR contacts are those employees of an LIR who are > > > > registered with > > > > > > > RIPE NCC as authoritative contact persons. > > > > > > > > > > > > > > It is expected that most of those interested in > the Routing > > > > > > > Registry Training Course will not be an > > authoritative contact > > > > > > > person for their LIR, and therefore will be, refused by > > > > the course > > > > > > > registration "robot". In order to be admitted to > > the course, a > > > > > > > confirmation e-mail must be sent to > > <training(a)ripe.net>. Please > > > > > > > approach the LIR contacts from your organisation > personally, > > > > > > > since the identity of LIR contacts is > confidential, and the > > > > > > > RIPE NCC is > > > > > > > unable to divulge contact persons for any given LIR. > > > > > > > > > > > > > > Kind Regards, > > > > > > > Training Team > > > > > > > RIPE NCC > > > > > > > > > > > > > > > > ************************************************************** > > > > > > > ************** > > > > > > > > > > > > > > COURSE DATES AND VENUES > > > > > > > ======================== > > > > > > > > > > > > > > Date: Friday 15 October 2004 > > > > > > > Time: 0900 - 1700 > > > > > > > Location: Geneva, Switzerland > > > > > > > > > > > > > > AND: > > > > > > > Date: Tuesday 23 November 2004 > > > > > > > Time: 0900 - 1700 > > > > > > > Location: Damascus, Syria > > > > > > > > > > > > > > > > > > > > > AND: > > > > > > > Date: Friday 17 December 2004 > > > > > > > Time: 0900 - 1700 > > > > > > > Location: Amsterdam, the Netherlands > > > > > > > > > > > > > > > > ************************************************************** > > > > > > > *************** > > > > > > > > > > > > > > REGISTRATION FORM > > > > > > > ================= > > > > > > > > > > > > > > %START > > > > > > > > > > > > > > PART 1 - Registration > > > > > > > 1) Your name > > > > > > > Enter First name, Last name in full > > > > > > > e.g. John Doe > > > > > > > Mary-Beth Walton > > > > > > > > > > > > > > > > > > > > > # NAME [ ] > > > > > > > > > > > > > > 2) Your Registry ID (format: country-code.<name of > > registry>) > > > > > > > > > > > > > > # REG [ ] > > > > > > > > > > > > > > 3) Your e-mail address > > > > > > > > > > > > > > # EMAIL [ ] > > > > > > > > > > > > > > 4) Your NIC handle (optional) > > > > > > > > > > > > > > # NICHANDLE [ ] > > > > > > > > > > > > > > 5) The course you plan to attend (date and location) > > > > > > > > > > > > > > # COURSE [ ] > > > > > > > > > > > > > > %END > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > The Roman Rule: > > The one who says it cannot be done > > should never interrupt the one who is doing it. > > >

1 0

NCC#2004081420: No keepalive from Matthew
by Matthew Williams 24 Aug '04

24 Aug '04

Arife sent the guy a reply on the 20th that should've done the trick. Cheers, Matthew --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/

1 0

New RIS rawdata backup schedule
by Arife Vural 20 Aug '04

20 Aug '04

Just for your information: OPS took over the backup of rawdata from me. I passed all tapes to OPS. New backup schedule is: OPS keep two copy of the data, one is at OPS safe place and the other one is at ABN-Amro safe. Rawdata is written into tapes at OPS safe place once in a week (Firday's). For ABN-Amro, I do not know the schedule yet. OPS related doc is available at http://iii.ripe.net/ops/docs/areas/services/backup/risbackup.html OPS also will do zero level backup, but time schedule is not decided yet. I have updated RIS operational doc through the latest changes. http://iii.ripe.net/sed/twiki/bin/view/Doc/RISOperationalDocumentation Arife

1 0

Monday RIS meeting
by Arife Vural 20 Aug '04

20 Aug '04

Hi all, I'm not in next week, so I could not make RIS meeting. But, if you have any agenda items, please go and have the meeting. But, please do not forget to send minutes to the list. Arife

1 0

I'm not IN next week.
by Arife Vural 20 Aug '04

20 Aug '04

Hi guys, I'll be in London for training next week and most probably I could not read my RIPE NCC inbox. If you would need anything from me, please contact with me by personal e-mail or by phone, E-mail: arife(a)xs4all.nl Phone: +31 61 471 8561 Vasco will continue to check RIS inbox as he usually does. But, he might need some help about some user request. For those cases, if you guys, Matthew and James, can give a hand to him, I will be really appreaciated. Arife

1 0

Re: [ris-int] Re: RIPE NCC RIS box @ PAIX
by Paul Vixie 20 Aug '04

20 Aug '04

> > > i think i can do this. i'm working with the paix people now. > > I was wondering whether there is any progress about this issue. yes. after a brief scare, the new owners of PAIX ("switch and data") have decided not to throw ISC out of their facility after all. now, all that remains is to negotiate for another port on their switching fabric. it's likely that this will be granted. > If you could provide me the address to deliver the RIS box, I would > contact MAE-West people to arrange the delivery to PAIX. the best thing is if you have the mae-west people contact peter losher, who operates the f-root node at mae-west and who has therefore seen your host since we're in the same lab. peter will want to take your box back to ISC and then move it to a PAIX-connected location later on. it could be that we'll put it at PAIX, but it could also be that we'll put it at "200 paul" which also has PAIX connectivity. "200 paul" is where our other RIPE-owned box (204.152.184.211) is located. cc'ing plosher so he'll know what's going on.

2 1

Re: RIPE NCC RIS box @ PAIX
by Paul Vixie 19 Aug '04

19 Aug '04

i think i can do this. i'm working with the paix people now. > Date: Mon, 9 Aug 2004 15:03:34 +0200 > From: Arife Vural <arife(a)ripe.net> > To: vixie(a)isc.org, joao(a)isc.org, paul(a)vix.com > Cc: ris-int(a)ripe.net > Subject: RIPE NCC RIS box @ PAIX > User-Agent: Mutt/1.4.2.1i > X-Organization: RIPE Network Coordination Centre > X-FCOPY: arife(a)ripe.net > X-Phone: +31 20 535 4490 > X-Fax: +31 20 535 4445 > X-WWW: http://www.ripe.net > X-Operating-System: Linux x12 2.4.26 > X-RIPE-Spam-Level: > X-RIPE-Spam-Status: N 0.000000 / 0.0 / 0.0 / disabled > X-RIPE-Signature: 8eb633018b90ef9d380ed3af8868775b > > > Hi Joao, Paul, > > My name is Arife Vural. I'm working as Network Engineer for RIPE NCC RIS > (Routing Information Service) Project. We have remote route collectors > around the world to collect BGP routing data. > > Lately, the box we have at MAE-West is not as functional as we aimed. We > could not get enough peers there. Because of that we are looking for a new > place for RRC box on West coast. PAIX looks like a good choice for us by > looking at number of members and also network infrastructure. We are just > wondering whether you would help us to locate RIS box at PAIX. To do this, > we would need help at the beginning to install the box and do the network > connection. Other than that, we also need a transit provider to reach the > box. > > I'll be appreciated if you could get back to us whether you could help > or not about relocating the RIS box at PAIX. > > Kind regards. > Arife

3 4

RE: myASn in training
by Matthew Williams 18 Aug '04

18 Aug '04

> > Hi Matthew, all, > > let's meet to talk about it :) Will you make the C-time entry? > Will do. Who should be there? Arife, Arno, you and I? > On Tue, 17 Aug 2004 14:04:00 +0200 > "Matthew Williams" <matthew(a)ripe.net> wrote: > > > [thanks for the hook-up, Rumy] > > > > Hi Vesna, > > > > Arife should be included on this too. > > > > > Vesna: could you discuss this with Matthew (and if necessary > > > Arno and/or > > > Ferenc) and let me know what your thoughts are? > > > > Include a section in rr training? > > > > We already have one slide in the RR course about the myASn; > sometimes we used to show the demo (but I think my account > expired...). Nope, should be okay unless you're trying to access the old prototype. > > We can maybe change that -- depending on how much attention > you want to give to this service, and how much space we can > "free-up" in the curent course, and how it fits with the rest > of topics.. > > Personally, I would prefere if we can do some hands-on with > the "myASn", but that would require opening 20 (or 5?) > demo-accounts for each course, thinking of the tasks to give > to the participants (or sub-groups), deciding what are the > most useful features to let them see/practice, how much time > it takes to do all that etc... > > I guess this brain-dump puts some of the topics on the agenda > for the meeting :) Fine. Cheers, Matthew > > > Cheers, > > Matthew > > > > ciao, > becha > > > > > -----Original Message----- > > > From: Rumy Kanis [mailto:rumy@ripe.net] > > > Sent: 17 August 2004 13:55 > > > To: Matthew Williams; 'Rumy Kanis'; becha(a)ripe.net > > > Cc: 'Henk Uijterwaal'; 'Matthew Williams' > > > Subject: myASn in training > > > > > > > > > Hi Matthew, > > > > > > I am sort of getting back up to speed again :-) but still > > > drowning in my mails. > > > > > > I am including Vesna in this reply, I think it would be best > > > if you discuss > > > this with her. Vesna has the overall responsibility over the > > > different > > > training courses and their content (Arno has > responsibility over the > > > advanced courses, Ferenc over the LIR). Vesna will have a good > > > understanding of whether this fits into one of our trainings > > > and if so, > > > into which one and in what format. > > > > > > Vesna: could you discuss this with Matthew (and if necessary > > > Arno and/or > > > Ferenc) and let me know what your thoughts are? > > > > > > Thanks! > > > > > > Cheers, > > > Rumy > > > > > > > > > At 02:37 PM 7/29/2004 +0200, Matthew Williams wrote: > > > >Hi Rumy, > > > > > > > >I see that you're on VAC until mid-Aug. Please get back > to me when > > > >you're > > > >up to speed again. > > > > > > > >Hope hols were relaxing :) > > > > > > > >Cheers, > > > >Matthew > > > > > > > > > -----Original Message----- > > > > > From: Matthew Williams [mailto:matthew@ripe.net] > > > > > Sent: 22 July 2004 18:02 > > > > > To: 'Rumy Kanis' > > > > > Cc: 'Henk Uijterwaal' > > > > > Subject: FW: Announcement Routing Registry Training Courses > > > > > > > > > > > > > > > Hi Rumy, > > > > > > > > > > Henk suggested that I get in touch with you about > > > including a myASn > > > > > section into one of your trainings. Version 1 will be > > > ready before > > > > > the next RIPE meeting. Any thoughts? ;) > > > > > > > > > > Cheers, > > > > > Matthew > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: routing-wg-admin(a)ripe.net > > > [mailto:routing-wg-admin@ripe.net] > > > > > > On Behalf Of RIPE NCC Training > > > > > > Sent: 21 July 2004 16:27 > > > > > > To: local-ir(a)ripe.net; db-wg(a)ripe.net; routing-wg(a)ripe.net; > > > > > > irrtoolset(a)ripe.net > > > > > > Subject: Announcement Routing Registry Training Courses > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dear Colleagues, > > > > > > > > > > > > [apologies for duplicate postings] > > > > > > > > > > > > As a service to its members the RIPE NCC offers the "Routing > > > > > > Registry Training Course". > > > > > > > > > > > > The main objective of the "Routing Registry Training > > > Course" is to > > > > > > familiarise the LIRs with the features of the Routing > > > > > > Registry, > > > > > > while introducing the relevant tools and services of > > > the RIPE NCC. > > > > > > The course also offers practical exercises. > > > > > > > > > > > > OVERVIEW OF TOPICS COVERED IN THE COURSE: > > > > > > - Routing Registry as a part of the RIPE Whois Database and > > > > > > the > > > > > > Internet Routing Registry (IRR) > > > > > > - Specifying routing policies using (RPSL) > > > > > > Routing Policy Specification Language and the RtConfig tool > > > > > > - IRRToolSet > > > > > > - Routing Information Service (RIS) > > > > > > - Routing Registry Consistency Check Project > > > > > > > > > > > > Please note that this is an advanced course. It will: > > > > > > - NOT teach the basics of routing > > > > > > - NOT teach the basics of RIPE Database operations, > > > > > > - NOT describe how to receive Internet resources from > > > the RIPE NCC > > > > > > - NOT describe how to operate a Local Internet > Registry (LIR) > > > > > > > > > > > > The target audience of the course are technical staff of > > > > > > LIRs: e.g. network operators, engineers etc. This course is > > > > > > not > > > > > > intended for administrative or management staff (e.g. > > > > > > Hostmasters) . It is assumed that all attendees will be > > > > > familiar with > > > > > > Border Gateway Protocol routing and with the RIPE > > > Database (i.e. > > > > > > creating/modifying objects). > > > > > > > > > > > > This course is based on interactive exercises in a > > > local network > > > > > > set-up. Please bring your laptops equipped with the > > > > > following: > > > > > > - A working Ethernet card, > > > > > > - Three meters of Ethernet cable, > > > > > > - A secure connection client, > > > > > > - A web browser. > > > > > > > > > > > > Please be prepared to share your laptop (or at least > > > allow another > > > > > > attendee to "look over your shoulder") if necessary. > > > > > > > > > > > > The Routing Registry Training Course is conducted in > > > the English > > > > > > language and is free of charge, since it is covered by the > > > > > > membership fee. > > > > > > > > > > > > More information about the Routing Registry Training > > > Course can be > > > > > > found > > > > > > at: http://www.ripe.net/training/rr/ > > > > > > > > > > > > REGISTRATION: > > > > > > > > > > > > You can register for a Routing Registry Training > Course at the > > > > > > following URL: > http://www.ripe.net/cgi-bin/trainingform.pl.cgi > > > > > > > > > > > > Or by completing the registration form at the end of > > > this e-mail > > > > > > and replying to <training(a)ripe.net> . In order to > > > register for a > > > > > > Routing Registry Training Course you must be an > > > employee of an LIR > > > > > > and either: > > > > > > - be an LIR contact > > > > > > - be confirmed by an LIR contact > > > > > > > > > > > > LIR contacts are those employees of an LIR who are > > > registered with > > > > > > RIPE NCC as authoritative contact persons. > > > > > > > > > > > > It is expected that most of those interested in the Routing > > > > > > Registry Training Course will not be an > authoritative contact > > > > > > person for their LIR, and therefore will be, refused by > > > the course > > > > > > registration "robot". In order to be admitted to > the course, a > > > > > > confirmation e-mail must be sent to > <training(a)ripe.net>. Please > > > > > > approach the LIR contacts from your organisation personally, > > > > > > since the identity of LIR contacts is confidential, and the > > > > > > RIPE NCC is > > > > > > unable to divulge contact persons for any given LIR. > > > > > > > > > > > > Kind Regards, > > > > > > Training Team > > > > > > RIPE NCC > > > > > > > > > > > > > ************************************************************** > > > > > > ************** > > > > > > > > > > > > COURSE DATES AND VENUES > > > > > > ======================== > > > > > > > > > > > > Date: Friday 15 October 2004 > > > > > > Time: 0900 - 1700 > > > > > > Location: Geneva, Switzerland > > > > > > > > > > > > AND: > > > > > > Date: Tuesday 23 November 2004 > > > > > > Time: 0900 - 1700 > > > > > > Location: Damascus, Syria > > > > > > > > > > > > > > > > > > AND: > > > > > > Date: Friday 17 December 2004 > > > > > > Time: 0900 - 1700 > > > > > > Location: Amsterdam, the Netherlands > > > > > > > > > > > > > ************************************************************** > > > > > > *************** > > > > > > > > > > > > REGISTRATION FORM > > > > > > ================= > > > > > > > > > > > > %START > > > > > > > > > > > > PART 1 - Registration > > > > > > 1) Your name > > > > > > Enter First name, Last name in full > > > > > > e.g. John Doe > > > > > > Mary-Beth Walton > > > > > > > > > > > > > > > > > > # NAME [ ] > > > > > > > > > > > > 2) Your Registry ID (format: country-code.<name of > registry>) > > > > > > > > > > > > # REG [ ] > > > > > > > > > > > > 3) Your e-mail address > > > > > > > > > > > > # EMAIL [ ] > > > > > > > > > > > > 4) Your NIC handle (optional) > > > > > > > > > > > > # NICHANDLE [ ] > > > > > > > > > > > > 5) The course you plan to attend (date and location) > > > > > > > > > > > > # COURSE [ ] > > > > > > > > > > > > %END > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > The Roman Rule: > The one who says it cannot be done > should never interrupt the one who is doing it. >

1 0

Re: [ripe.net #102454] [henk@ripe.net: Re: [ris-int] Re: RIPE NCC RIS box @ PAIX]
by James Aldridge 18 Aug '04

18 Aug '04

Rene Wilhelm wrote: > > > We do not have to make decision today. When Shane and James get > > back from vacation, I like to check with them. > > for what it's worth, I agree with Matthew and Henk to rename rrc08 > when it moves out of MAE WEST. It is the easiest clue to anyone > *using* the data that something drastically has changed. > > If you DO NOT rename rrc08, *everyone* using the data will have > to keep in mind at what day the machine moved from mae to paix. > RISreports, historic trends, graphs, will no longer be clear > by themselves, as with every oddity seen in rrc08, one will have > to check if it is before or after the move date. > > Why create that burden when NCC can simply rename to rrc14? I'd choose to go for rrc14 for all the same reasons. James

1 0

RIPE NCC RIS Project - De-Bogonising Update
by Arife Vural 17 Aug '04

17 Aug '04

Apologies for duplicate messages. Part of De-Bogonising New Address Blocks Activity, we are announcing prefixes from 85/8 on RRC03. Prefixes from 85/8 are now in regular production use so we are no longer announcing 85.192.0.0/16 and 85.255.248.0/21. If you have filters to accept those prefixes from AS12654, please update them accordingly. Kind regards. Arife

1 0

risintro
by Matthew Williams 17 Aug '04

17 Aug '04

BTW, you should also link to de-cix. http://www.ripe.net/ripencc/pub-services/np/ris/de-cix.html What was wrong with http://www.ripe.net/ris/risintro.html? I think it's a shame that you have dropped this promo opportunity for "other services", and promo lies with NP, no?. Remember, the RIS is a part of a whole package: +++ Useful Links * RIS Home Page * myASn * RISwhois * BGPlay * More RIS Tools * Weekly RIS Statistics Report * RIS Raw Data * RIS Looking Glass Other Services and Projects * K-root Local Mirror Instances * Test Traffic Measurements (TTM) * RIPE NCC DNS Monitoring (dnsmon) * Deployment of Internet Security Infrastructures (DISI) +++ Cheers, Matthew --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/

3 8

Fw: NCC#2004081626 [Re: Test allocations]
by RIS 17 Aug '04

17 Aug '04

FYI: rrc03 is stopped announcing those prefixes. I removed route object entries from RIPE DB as well. Arife ----- Begin forwarded message ----- Date: Tue, 17 Aug 2004 09:49:38 +0200 From: Mike Petuschak <mike(a)ripe.net> To: RIS <ris-request(a)ripe.net> Subject: Re: NCC#2004081626 Test allocations Message-Id: <20040817074938.GA3324(a)ripe.net> Dear Arife, Please only remove the ranges from 85/8, i.e. network 85.192.0.0/16 network 85.255.248.0/21 the following route objects needs to be removed too: route: 85.192.0.0/16 descr: RIPE-NCC-RIS New Allocation Filter Checking origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20040402 source: RIPE route: 85.255.248.0/21 descr: RIPE-NCC-RIS New Allocation Filter Checking origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20040402 source: RIPE

1 0

[henk@ripe.net: Re: [ris-int] Re: RIPE NCC RIS box @ PAIX]
by Arife Vural 17 Aug '04

17 Aug '04

Hi guys, To re-locate RRC08, do we need any re-installation or not? Is changing IP config either at old or new location enough? Arife ----- Forwarded message from "Henk Uijterwaal (RIPE NCC)" <henk(a)ripe.net> ----- From: "Henk Uijterwaal (RIPE NCC)" <henk(a)ripe.net> To: Arife Vural <arife(a)ripe.net> Subject: Re: [ris-int] Re: RIPE NCC RIS box @ PAIX Date: Mon, 16 Aug 2004 10:29:51 +0200 (CEST) Cc: ris-int(a)ripe.net On Sat, 14 Aug 2004, Arife Vural wrote: > > > i think i can do this. i'm working with the paix people now. > > That's great :-) OK, please let me know if you need anything > from me. I'd think that we have to prepare reconfiguration, shutdown @ MAE-W, shipping to PAIX etc. ourselves first, Henk > > Arife > ------------------------------------------------------------------------------ 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). ----- End forwarded message -----

5 14

Re: [ripe.net #102454] [henk@ripe.net: Re: [ris-int] Re: RIPE NCC RIS box @ PAIX]
by Rene Wilhelm 16 Aug '04

16 Aug '04

> We do not have to make decision today. When Shane and James get > back from vacation, I like to check with them. for what it's worth, I agree with Matthew and Henk to rename rrc08 when it moves out of MAE WEST. It is the easiest clue to anyone *using* the data that something drastically has changed. If you DO NOT rename rrc08, *everyone* using the data will have to keep in mind at what day the machine moved from mae to paix. RISreports, historic trends, graphs, will no longer be clear by themselves, as with every oddity seen in rrc08, one will have to check if it is before or after the move date. Why create that burden when NCC can simply rename to rrc14? -- Rene

1 0

This page
by Matthew Williams 16 Aug '04

16 Aug '04

>Please send your comments to <ris-int(a)ripe.net> http://www.ripe.net/ripencc/pub-services/np/ris/de-cix.html Change to ris(a)ripe.net? Cheers, Matthew --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/

2 1

FYI: riswhois up-to-date monitoring
by Rene Wilhelm 16 Aug '04

16 Aug '04

Hi Arife, Ops/gerard have setup monitoring to alarm us when riswhois fails to refresh its BGP data. The daemon should read latest BGP fulldump files every 8 hours, but few weeks ago I noticed it failed to that; hence the request to ops. Do you also have independent checks (in ops or sed) to see if bgp dump files are collected to halfweg? -- Rene ------- Forwarded Message X-Recipient: <wilhelm(a)mailhost.ripe.net> Return-Path: <rt2(a)ripe.net> Received: from owl.ripe.net (owl.ripe.net [193.0.1.100]) by birch.ripe.net (8.12.10/8.11.6) with ESMTP id i7D9nlW7023703 for <wilhelm(a)mailhost.ripe.net>; Fri, 13 Aug 2004 11:49:47 +0200 Received: (from rt2@localhost) by owl.ripe.net (8.12.10/8.12.6) id i7D9nl4T015909; Fri, 13 Aug 2004 11:49:47 +0200 Date: Fri, 13 Aug 2004 11:49:47 +0200 Subject: Re: [ripe.net #102281] R: intelligent monitoring From: Gerard Leurs via RT <ops(a)ripe.net> Reply-To: ops(a)ripe.net In-Reply-To: <rt-102281(a)ripe.net> Message-ID: <rt-102281-491055.1.96152598629475(a)ripe.net> Precedence: bulk X-RT-Loop-Prevention: ripe.net RT-Ticket: ripe.net #102281 Managed-by: Request Tracker 2.0.9 (http://www.fsck.com/projects/rt/) RT-Originator: RT::User 10 To: wilhelm(a)ripe.net X-UIDL: 7WB!!]+k"!OUE"!>?&#! Rene. WE now have a check for riswhois sources 'RISSOURCES'. The nagioscheck runs every 120 minutes. And an email is send when the difference is >2 days. Closing ticket. Gerard. ------- End of Forwarded Message

2 1

Web Access Report for the Routing Information Service - July, 2004
by Matthew Williams 12 Aug '04

12 Aug '04

Hi All, The monthly RIS Web Access Report is available at the following URL: http://iii.ripe.net/np/ris/WWW072004_RIS.pdf Please comment on oddities. Cheers, Matthew

1 0

O: myas (no N) go away
by Matthew Williams 12 Aug '04

12 Aug '04

Hereby I wish to notify Operations of something uncategorised. Detailed description: --------------------- Hotseat wrote: > This request will be closed. You can create a new one to > tell us what you really want. > > E m i l . "Yo, I'll tell you what I want, what I really really want, So tell me what you want, what you really really want, I'll tell you what I want, what I really really want, So tell me what you want, what you really really want, I wanna, I wanna, I wanna, I wanna, I wanna really really really wanna zigazig ha." [ Please provide us with all relevant information ] New request: > As Rene points out, all I ever wanted was: > > - Eliminate the myastesting (no N) link on > http://www.ripe.net/ripencc/mail-archives/. > > - I also doubt that we need the alias - myastesting (no N) - > any longer. > > Can this be done without touching/deleting myasntesting (with N)? Regards, Matthew Williams

2 1

RIS related docs
by Arife Vural 12 Aug '04

12 Aug '04

Hi guys, Some of the RIS related docs are at http://iii.ripe.net/sed/twiki/bin/view/Doc/RIS. After Kevin does the re-arrangement on SED iii pages, some of the stuff from NP pages will go there as well. Arife

2 2

NP and SED = RIS
by Matthew Williams 12 Aug '04

12 Aug '04

Hi Arife, I think this will be last time that I will take on a myASn task. Next time, I'll just send you an email. A lot easier that way... I've learnt my lesson ;) My open RIS items concern: - Admin for MSK-IX - Promoting myASn at R49 - RIS Update at R49 - myASn User doc - Working with guys on odd myASn issue that may pop up - New RIS www Does this cover it? Cheers, Matthew > -----Original Message----- > From: ris-int-admin(a)ripe.net [mailto:ris-int-admin@ripe.net] > On Behalf Of Matthew Williams > Sent: 11 August 2004 20:08 > To: RIPE NCC Operations > Cc: ris-int(a)ripe.net > Subject: [ris-int] O: myas (no N) go away > > > > Hereby I wish to notify Operations of something uncategorised. > > Detailed description: > --------------------- > Hotseat wrote: > > This request will be closed. You can create a new one to > tell us what > > you really want. > > > > E m i l . > > "Yo, I'll tell you what I want, what I really really want, > So tell me what you want, what you really really want, > I'll tell you what I want, what I really really want, > So tell me what you want, what you really really want, > I wanna, I wanna, I wanna, I wanna, I wanna really > really really wanna zigazig ha." > > [ Please provide us with all relevant information ] > > New request: > > As Rene points out, all I ever wanted was: > > > > - Eliminate the myastesting (no N) link on > > http://www.ripe.net/ripencc/mail-archives/. > > > > - I also doubt that we need the alias - myastesting (no N) - > > any longer. > > > > Can this be done without touching/deleting myasntesting (with N)? > > Regards, > Matthew Williams >

2 1

Re: [ris-int] RE: [ripe.net #102308] R: myas go away
by Rene Wilhelm 11 Aug '04

11 Aug '04

Hi, > > So to correct this, I suggest: > > > > 1. rm -rf /ncc/maillists/archives/pub/myasntesting > > 2. mv /ncc/maillists/archives/pub/myastesting > > /ncc/maillists/archives/pub/myasntesting 3. restore the myasntesting > > list (all subscribers and settings) > > Steps 1&2 seem to be contradicting: > > 1. throw away newest and active archive > 2. copy old obsolete and inactive archive over the (now empty) current > archives. If you took 1 minute (or 30 seconds) to LOOK at these archives, you would see that myastesting has EVERYTHING from myastesting PLUS the stuff send to myasntesting myasntesting on the other hand ONLY has stuff send to myasntesting. so to preserve the history of the myas(n) testing list, one should keep myastesting. As I said, this is something that SHOULD have been done in the first place when the mailing list changed name. > Again, this messup has been corrected and for all I care the ticket is > closed for being a poor request. huh? the request seemed pretty clear to me. You can't expect users to know all the intricate details of the convoluted setup of mailing lists and their archives. -- Rene

1 0

RE: [ripe.net #102308] R: myas go away
by Matthew Williams 11 Aug '04

11 Aug '04

Hi Emil, I see, it was my fault all along for OPS doing something that I never requested. Ever seen the Fawlty Towers episode where Basil spanks himself on the bottom? ;) Anyway, that said, many thanks for fixing this. Much obliged :) As Rene points out, all I ever wanted was: - Eliminate the myastesting (no N) link on http://www.ripe.net/ripencc/mail-archives/. - I also doubt that we need the alias - myastesting (no N) - any longer. Can this be done without touching/deleting myasntesting (with N)? Kind regards, Matthew > -----Original Message----- > From: FLS Hotseat via RT [mailto:ops@ripe.net] > Sent: 11 August 2004 19:00 > To: matthew(a)ripe.net > Subject: Re: [ripe.net #102308] R: myas go away > > > > Hi Matthew, > > Jeannette has gone home, so this is 'hotseat' (Emil) speaking: > > > On Wed, 11 Aug 2004 18:30:10 +0200, "Matthew Williams" > <matthew(a)ripe.net> wrote: > > > > myasntesting. That's why I removed this list (myasntesting). > > > > This is not want I wanted. If anything was unclear, you should have > > gotten back to me before deleting something that I had > hoped would've > > been left untouched. > > Your first mail was a very poorly formatted forward of a forward of > a...etc. In fact you have not formulated a request.. If you > say we shoud have bounced it for being unclear, I totally agree! > > I am not at all surprised that it was not correctly > interpreted. Next time spend some time on making a clear > request please. > > On to the real issue: "myastesting" was an alias to > "myasNtesting", not a list in itself. To stop all confusion I > have put that alias back in place; nothing has disappeared, > nothing has changed, only time was wasted. > > This request will be closed. You can create a new one to > tell us what you really want. > > E m i l . > > > x7:emil:~ $ telnet birch 25 > Trying 193.0.1.96... > Connected to birch. > Escape character is '^]'. > 220 birch.ripe.net ESMTP RIPE NCC Sendmail 8.12.10; Wed, 11 > Aug 2004 18:54:50 +0200 expn myastesting 250 2.1.5 > <myasntesting(a)lists.ripe.net> expn myasntesting 250 2.1.5 > <myasntesting(a)lists.ripe.net> quit 221 2.0.0 birch.ripe.net > closing connection Connection closed by foreign host. x7:emil:~ $ >

1 0

Re: [ris-int] RE: [ripe.net #102308] R: myas go away
by Rene Wilhelm 11 Aug '04

11 Aug '04

Hmm, this seems to have headed off in quite the wrong direction, a request to delete an obsolete mail archive resulting in removal of an active mail list :( To shed some light on the matter: http://www.ripe.net/ripencc/mail-archives/ lists both myasntesting and myastesting, the latter holding identical messages to myasntesting for at least all of 2004 All that Matthew wanted was the obsoleted myastesting (without 'n') to disappear from this listing and stop being a valid e-mail address. It appears that way back in the distant past, when the project was renamed from myAS to myASn and the myasntesting list took over from myastesting, some mistakes have been made in the archive setup: - the myastesting archive SHOULD have been renamed mysasntesting - the myastesting alias should NOT have continued archiving. So to correct this, I suggest: 1. rm -rf /ncc/maillists/archives/pub/myasntesting 2. mv /ncc/maillists/archives/pub/myastesting /ncc/maillists/archives/pub/myasntesting 3. restore the myasntesting list (all subscribers and settings) 4. (re)activate archiving of myasntesting -- Rene > > myasntesting. That's why I removed this list (myasntesting). > > This is not want I wanted. If anything was unclear, you should have gotten back to me before deleting something that I had hoped > would've been left untouched. > > Cheers, > Matthew > > > -----Original Message----- > > From: Jeannette Decades via RT [mailto:ops@ripe.net] > > Sent: 11 August 2004 18:22 > > To: matthew(a)ripe.net > > Subject: RE: [ripe.net #102308] R: myas go away > > > > > > Hi, > > > > There has never been no myastesting. There's only an alias > > which points to > > myasntesting. That's why I removed this list (myasntesting). > > Tonight the systems will be synced and our mailserver will > > then not know of > > myastesting(a)ripe.net nor myasntesting(a)ripe.net > > > > > > Jean. > > #301 > > > > At 05:59 PM 8/11/2004 +0200, you wrote: > > >Hi Jean, > > > > > > > > > * Please get rid of myastesting. I believe myasntesting > > > > > > cross-references it (p > > > > > > * lease verify). > > > > > > > Removed list myasntesting (kept archives) and alias myastesting. > > > > > >Wait please, not _myasntesting_, see above it says > > _myastesting_ (w/o > > >'n'). > > > > > >Cheers, > > >Matthew > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > From: Jeannette Decades via RT [mailto:ops@ripe.net] > > > > Sent: 11 August 2004 15:27 > > > > To: matthew(a)ripe.net > > > > Subject: Re: [ripe.net #102308] R: myas go away > > > > > > > > > > > > Hi Matthew, > > > > > > > > Removed list myasntesting (kept archives) and alias myastesting. > > > > > > > > Can this go too? > > > > myasn-bounce: /dev/null > > > > > > > > cheers, > > > > Jean. > > > > > > > > At 03:02 PM 8/11/2004 +0200, you wrote: > > > > > > > > > > > > >Hereby I wish to request a service from Operations. > > > > > > > > > >Detailed description: > > > > >--------------------- > > > > > > > > > >[ Please provide us with all relevant information ] > > > > > > > > > > > -----Original Message----- > > > > > > From: ris-int-admin(a)ripe.net > > [mailto:ris-int-admin@ripe.net] On > > > > > > Behalf Of RIPE > > NCC Webmaster > > > > > > Sent: 11 August 2004 09:02 > > > > > > To: Matthew Williams > > > > > > Cc: ris-int(a)ripe.net > > > > > > Subject: [ris-int] Re: > > > > > > http://www.ripe.net/ripencc/mail-archives/ > > > > > > > > > > > > > > > > > > Good Morning Matthew > > > > > > > > > > > > The mailing lists on Mailman are controlled by Ops, so I > > > > guess the > > > > > > request needs to head in their direction. > > > > > > > > > > > > Adrian > > > > > > > > > > > > > > > > > > > > > > > > "Matthew Williams" <matthew(a)ripe.net> writes: > > > > > > * Hi Webbies, > > > > > > * > > > > > > * Please get rid of myastesting. I believe myasntesting > > > > > > cross-references it (p > > > > > > * lease verify). > > > > > > * > > > > > > * http://www.ripe.net/ripencc/mail-archives/ > > > > > > * > > > > > > * Cheers, > > > > > > * Matthew > > > > > > * > > > > > > * --- > > > > > > * > Matthew Williams (MW243-RIPE) > > > > > > * > Customer Liaison Engineer > > > > > > * > RIPE NCC - http://www.ripe.net/np/ > > > > > > * > > > > > > > > > > > > > > > > > > > > > > > > > >Regards, > > > > > Matthew Williams > > > > > > >

2 1

FW: [ris-int] RE: [ripe.net #102308] R: myas go away
by Matthew Williams 11 Aug '04

11 Aug '04

Can the list be restored? Or can we do something so users mailing to the list don't just bounce? If you have any way of finding the subscribed folk again then that would be of great help. Cheers, Matthew > -----Original Message----- > From: ris-int-admin(a)ripe.net [mailto:ris-int-admin@ripe.net] > On Behalf Of Matthew Williams > Sent: 11 August 2004 18:30 > To: ops(a)ripe.net > Cc: ris-int(a)ripe.net > Subject: [ris-int] RE: [ripe.net #102308] R: myas go away > > > > myasntesting. That's why I removed this list (myasntesting). > > This is not want I wanted. If anything was unclear, you > should have gotten back to me before deleting something that > I had hoped would've been left untouched. > > Cheers, > Matthew > > > -----Original Message----- > > From: Jeannette Decades via RT [mailto:ops@ripe.net] > > Sent: 11 August 2004 18:22 > > To: matthew(a)ripe.net > > Subject: RE: [ripe.net #102308] R: myas go away > > > > > > Hi, > > > > There has never been no myastesting. There's only an alias > > which points to > > myasntesting. That's why I removed this list (myasntesting). > > Tonight the systems will be synced and our mailserver will > > then not know of > > myastesting(a)ripe.net nor myasntesting(a)ripe.net > > > > > > Jean. > > #301 > > > > At 05:59 PM 8/11/2004 +0200, you wrote: > > >Hi Jean, > > > > > > > > > * Please get rid of myastesting. I believe myasntesting > > > > > > cross-references it (p > > > > > > * lease verify). > > > > > > > Removed list myasntesting (kept archives) and alias myastesting. > > > > > >Wait please, not _myasntesting_, see above it says > > _myastesting_ (w/o > > >'n'). > > > > > >Cheers, > > >Matthew > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > From: Jeannette Decades via RT [mailto:ops@ripe.net] > > > > Sent: 11 August 2004 15:27 > > > > To: matthew(a)ripe.net > > > > Subject: Re: [ripe.net #102308] R: myas go away > > > > > > > > > > > > Hi Matthew, > > > > > > > > Removed list myasntesting (kept archives) and alias myastesting. > > > > > > > > Can this go too? > > > > myasn-bounce: /dev/null > > > > > > > > cheers, > > > > Jean. > > > > > > > > At 03:02 PM 8/11/2004 +0200, you wrote: > > > > > > > > > > > > >Hereby I wish to request a service from Operations. > > > > > > > > > >Detailed description: > > > > >--------------------- > > > > > > > > > >[ Please provide us with all relevant information ] > > > > > > > > > > > -----Original Message----- > > > > > > From: ris-int-admin(a)ripe.net > > [mailto:ris-int-admin@ripe.net] On > > > > > > Behalf Of RIPE > > NCC Webmaster > > > > > > Sent: 11 August 2004 09:02 > > > > > > To: Matthew Williams > > > > > > Cc: ris-int(a)ripe.net > > > > > > Subject: [ris-int] Re: > > > > > > http://www.ripe.net/ripencc/mail-archives/ > > > > > > > > > > > > > > > > > > Good Morning Matthew > > > > > > > > > > > > The mailing lists on Mailman are controlled by Ops, so I > > > > guess the > > > > > > request needs to head in their direction. > > > > > > > > > > > > Adrian > > > > > > > > > > > > > > > > > > > > > > > > "Matthew Williams" <matthew(a)ripe.net> writes: > > > > > > * Hi Webbies, > > > > > > * > > > > > > * Please get rid of myastesting. I believe myasntesting > > > > > > cross-references it (p > > > > > > * lease verify). > > > > > > * > > > > > > * http://www.ripe.net/ripencc/mail-archives/ > > > > > > * > > > > > > * Cheers, > > > > > > * Matthew > > > > > > * > > > > > > * --- > > > > > > * > Matthew Williams (MW243-RIPE) > > > > > > * > Customer Liaison Engineer > > > > > > * > RIPE NCC - http://www.ripe.net/np/ > > > > > > * > > > > > > > > > > > > > > > > > > > > > > > > > >Regards, > > > > > Matthew Williams > > > > > > >

1 0

RE: [ripe.net #102308] R: myas go away
by Matthew Williams 11 Aug '04

11 Aug '04

> myasntesting. That's why I removed this list (myasntesting). This is not want I wanted. If anything was unclear, you should have gotten back to me before deleting something that I had hoped would've been left untouched. Cheers, Matthew > -----Original Message----- > From: Jeannette Decades via RT [mailto:ops@ripe.net] > Sent: 11 August 2004 18:22 > To: matthew(a)ripe.net > Subject: RE: [ripe.net #102308] R: myas go away > > > Hi, > > There has never been no myastesting. There's only an alias > which points to > myasntesting. That's why I removed this list (myasntesting). > Tonight the systems will be synced and our mailserver will > then not know of > myastesting(a)ripe.net nor myasntesting(a)ripe.net > > > Jean. > #301 > > At 05:59 PM 8/11/2004 +0200, you wrote: > >Hi Jean, > > > > > > > * Please get rid of myastesting. I believe myasntesting > > > > > cross-references it (p > > > > > * lease verify). > > > > > Removed list myasntesting (kept archives) and alias myastesting. > > > >Wait please, not _myasntesting_, see above it says > _myastesting_ (w/o > >'n'). > > > >Cheers, > >Matthew > > > > > > > > > > > > > -----Original Message----- > > > From: Jeannette Decades via RT [mailto:ops@ripe.net] > > > Sent: 11 August 2004 15:27 > > > To: matthew(a)ripe.net > > > Subject: Re: [ripe.net #102308] R: myas go away > > > > > > > > > Hi Matthew, > > > > > > Removed list myasntesting (kept archives) and alias myastesting. > > > > > > Can this go too? > > > myasn-bounce: /dev/null > > > > > > cheers, > > > Jean. > > > > > > At 03:02 PM 8/11/2004 +0200, you wrote: > > > > > > > > > >Hereby I wish to request a service from Operations. > > > > > > > >Detailed description: > > > >--------------------- > > > > > > > >[ Please provide us with all relevant information ] > > > > > > > > > -----Original Message----- > > > > > From: ris-int-admin(a)ripe.net > [mailto:ris-int-admin@ripe.net] On > > > > > Behalf Of RIPE > NCC Webmaster > > > > > Sent: 11 August 2004 09:02 > > > > > To: Matthew Williams > > > > > Cc: ris-int(a)ripe.net > > > > > Subject: [ris-int] Re: > > > > > http://www.ripe.net/ripencc/mail-archives/ > > > > > > > > > > > > > > > Good Morning Matthew > > > > > > > > > > The mailing lists on Mailman are controlled by Ops, so I > > > guess the > > > > > request needs to head in their direction. > > > > > > > > > > Adrian > > > > > > > > > > > > > > > > > > > > "Matthew Williams" <matthew(a)ripe.net> writes: > > > > > * Hi Webbies, > > > > > * > > > > > * Please get rid of myastesting. I believe myasntesting > > > > > cross-references it (p > > > > > * lease verify). > > > > > * > > > > > * http://www.ripe.net/ripencc/mail-archives/ > > > > > * > > > > > * Cheers, > > > > > * Matthew > > > > > * > > > > > * --- > > > > > * > Matthew Williams (MW243-RIPE) > > > > > * > Customer Liaison Engineer > > > > > * > RIPE NCC - http://www.ripe.net/np/ > > > > > * > > > > > > > > > > > > > > > > > > > > >Regards, > > > > Matthew Williams > > > >

1 0

Re: [ris-int] Re: myASn acc's
by Arife Vural 11 Aug '04

11 Aug '04

Hi Matthew, I have updated the script, now it's at risops@halfweg:myasn/bin/add_myasn_user. It does few checks and also documentation is available at http://iii.ripe.net/sed/twiki/bin/view/Doc/RIS. Just for your info. I will remove the old versions. Please, send me the link for mailinglist and password as well to update the list. Arife

2 1

RE: [ripe.net #102308] R: myas go away
by Matthew Williams 11 Aug '04

11 Aug '04

Hi Jean, > > > * Please get rid of myastesting. I believe myasntesting > > > cross-references it (p > > > * lease verify). > Removed list myasntesting (kept archives) and alias myastesting. Wait please, not _myasntesting_, see above it says _myastesting_ (w/o 'n'). Cheers, Matthew > -----Original Message----- > From: Jeannette Decades via RT [mailto:ops@ripe.net] > Sent: 11 August 2004 15:27 > To: matthew(a)ripe.net > Subject: Re: [ripe.net #102308] R: myas go away > > > Hi Matthew, > > Removed list myasntesting (kept archives) and alias myastesting. > > Can this go too? > myasn-bounce: /dev/null > > cheers, > Jean. > > At 03:02 PM 8/11/2004 +0200, you wrote: > > > >Hereby I wish to request a service from Operations. > > > >Detailed description: > >--------------------- > > > >[ Please provide us with all relevant information ] > > > > > -----Original Message----- > > > From: ris-int-admin(a)ripe.net [mailto:ris-int-admin@ripe.net] On > > > Behalf Of RIPE NCC Webmaster > > > Sent: 11 August 2004 09:02 > > > To: Matthew Williams > > > Cc: ris-int(a)ripe.net > > > Subject: [ris-int] Re: http://www.ripe.net/ripencc/mail-archives/ > > > > > > > > > Good Morning Matthew > > > > > > The mailing lists on Mailman are controlled by Ops, so I > guess the > > > request needs to head in their direction. > > > > > > Adrian > > > > > > > > > > > > "Matthew Williams" <matthew(a)ripe.net> writes: > > > * Hi Webbies, > > > * > > > * Please get rid of myastesting. I believe myasntesting > > > cross-references it (p > > > * lease verify). > > > * > > > * http://www.ripe.net/ripencc/mail-archives/ > > > * > > > * Cheers, > > > * Matthew > > > * > > > * --- > > > * > Matthew Williams (MW243-RIPE) > > > * > Customer Liaison Engineer > > > * > RIPE NCC - http://www.ripe.net/np/ > > > * > > > > > > > > > > >Regards, > > Matthew Williams >

1 0

R: myas go away
by Matthew Williams 11 Aug '04

11 Aug '04

Hereby I wish to request a service from Operations. Detailed description: --------------------- [ Please provide us with all relevant information ] > -----Original Message----- > From: ris-int-admin(a)ripe.net [mailto:ris-int-admin@ripe.net] > On Behalf Of RIPE NCC Webmaster > Sent: 11 August 2004 09:02 > To: Matthew Williams > Cc: ris-int(a)ripe.net > Subject: [ris-int] Re: http://www.ripe.net/ripencc/mail-archives/ > > > Good Morning Matthew > > The mailing lists on Mailman are controlled by Ops, so I > guess the request needs to head in their direction. > > Adrian > > > > "Matthew Williams" <matthew(a)ripe.net> writes: > * Hi Webbies, > * > * Please get rid of myastesting. I believe myasntesting > cross-references it (p > * lease verify). > * > * http://www.ripe.net/ripencc/mail-archives/ > * > * Cheers, > * Matthew > * > * --- > * > Matthew Williams (MW243-RIPE) > * > Customer Liaison Engineer > * > RIPE NCC - http://www.ripe.net/np/ > * > Regards, Matthew Williams

1 0

http://www.ripe.net/ripencc/mail-archives/
by Matthew Williams 11 Aug '04

11 Aug '04

Hi Webbies, Please get rid of myastesting. I believe myasntesting cross-references it (please verify). http://www.ripe.net/ripencc/mail-archives/ Cheers, Matthew --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/

2 1

myASn documentation
by Matthew Williams 10 Aug '04

10 Aug '04

Hi All, Please check: http://www.ris.ripe.net/myasn/help.html & http://www.ris.ripe.net/myasn/faq.html U: ris@12654 PW: risops And comment... Cheers, Matthew --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/

1 0

RIPE NCC RIS box @ PAIX
by Arife Vural 09 Aug '04

09 Aug '04

Hi Joao, Paul, My name is Arife Vural. I'm working as Network Engineer for RIPE NCC RIS (Routing Information Service) Project. We have remote route collectors around the world to collect BGP routing data. Lately, the box we have at MAE-West is not as functional as we aimed. We could not get enough peers there. Because of that we are looking for a new place for RRC box on West coast. PAIX looks like a good choice for us by looking at number of members and also network infrastructure. We are just wondering whether you would help us to locate RIS box at PAIX. To do this, we would need help at the beginning to install the box and do the network connection. Other than that, we also need a transit provider to reach the box. I'll be appreciated if you could get back to us whether you could help or not about relocating the RIS box at PAIX. Kind regards. Arife

1 0

myASn acc's
by Matthew Williams 09 Aug '04

09 Aug '04

Hi Arife, As agreed, please ticketize these requests. Cheers, Matthew

2 2

Notes from today's RIS meeting
by Arife Vural 09 Aug '04

09 Aug '04

Hi all, I tried to compile what we have discussed today in RIS meeting. Any comments/feedbacks are welcome. Arife -- - Matthew is in touch with Elena, from Moscow about installation of new RRCs. It's gonna be installed around 6 weeks. Matthew will also get IP address for the box and will pass to Bruce to burn new installation CDs. - Henk is in touch with George Michealson and Akira Kato about getting new peers at Tokyo. - Matthew made some changes on MyASN getting started docs, Arife will read and get back to Matthew if she has any questions or comments about it. - Arife and Matthew will get some usage stats about myASN usage to get an idea about the hardware requirements of - Putting a RRC box in Dubai is out of questions. Egypt might be an option, but we will gonna wait how AFRINIC project goes. - Arife will contact with Vixie and Damas about putting RRC08 to PAIX.

1 0

RIS meeting in 5 minutes!
by Arife Vural 09 Aug '04

09 Aug '04

1 0

SIX vs PAIX
by Matthew Williams 06 Aug '04

06 Aug '04

Pretty easy choice. Only concern is Route-Views presence. Cheers, Matthew SeattleIX: ---------- ~80 members (only ~40 core, ~10 connected via PAIX - incl WoodyNet and PCH, 7 listed 'not yet'?) Only 5 potential IPv6 peers of which only two listed as 'core' Only interesting if hosts offer transit Logistically slightly more problematic 'We don't know them' Potential Peers: http://www.seattleix.net/participants.htm Palo Alto IX: ------------- 130+ (many Asian providers) 10 potential IPv6 peers ISC, IIJ and Tiscali there (transit) Route-Views already there, however, they did go the LINX even though we were present 'Vixie and Damas connection useful' Potential Peers: http://www.switchanddata.com/Solutions/PAIX/Customers/PaloAlto/

1 0

new features
by Alexis Yushin 05 Aug '04

05 Aug '04

Hi, I finished xml.html please try it out, the templates are now provided in the form. I also have an experimental version of retromatch but it still needs some premission granting action from Arife. Everything else that was on the wish-list is finished, plus some extra's like myasn-admin delete to delete an entire registry and deleting all alarms in a group. I'm pretty much done. Since the project is finished, as far as my contract is concerned, I'd like to invite everybody to have a Columbus beer with me at 't IJ brewery. Suggestions for a specific date? Alexis

4 12

New Ris pages
by Matthew Williams 05 Aug '04

05 Aug '04

http://www4.ripe.net/projects/ris/ Shall we have a look together before this is made official? A lot has improved but some of the text still needs revising... Cheers, Matthew --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/

3 4

contact information
by Alexis Yushin 04 Aug '04

04 Aug '04

Hi, In case anyone needs to reach me after I'm done here: Alexis Yushin White Willow +31 65 427 0754 +31 20 670 7748 alexis(a)ww.net Alexis

1 0

myASn admin doc draft
by Alexis Yushin 02 Aug '04

02 Aug '04

Hi, This is a draft of the admin doc. Any comments/suggestions/critique or unrelated remarks are welcome :) Alexis 1. Overview This overview implies that the reader has familirized her/himself with the myASn user documentation and frequently asked questions. http://www.ris.ripe.net/myasn/help.html http://www.ris.ripe.net/myasn/faq.html myASn system internally consists basically of three parts: - frontend (web interface presently running on halfweg.ripe.net ) - backend (two perl demon scripts running on weesp.ripe.net ) - database (presently resided on weesp.ripe.net) Frontend consist of collection of Mason enabled web pages and help files that use perl libraries to access myASn database to configure the system and view the results of the processing done by backend. There are two versions of frontend: standalone and LIR Portal. The LIR Portal version of the frontend is not deployed at this moment and will be documented elsewhere. Everything below applies to the standalone version. Backend consist of two perl demon scripts: myasn-scan - that does the processing of the data and generates alarms that are stored in the myasn database myasn-send - that send the email notifications of the alarms that are generated by myasn-scan Both frontend and backend use the same set of perl modules. 2. myASn Installation pre-required modules: Alzabo::MethodMaker Alzabo::Runtime::Schema Apache::DBI DBI Exception::Class IO::Socket Lingua::EN::Inflect Mail::RFC822::Address Net::IP Socket Text::ASCIITable URI XML::Parser myASn installation on both frontend and backend servers should be as simple as checking the myASn package out of master CVS repository. export CVS_RSH=ssh export CVSROOT :ext:cow.ripe.net:/ncc/cvsroot cvs co myasn Further updates of myasn system can be simply done by issuing cvs up in the myasn directory. (use cvs -n up first, to see what's about to happen :) myASn system should be installed on both frontend and backend server into /home/risops/myasn directory. This directory is hard-coded into use lib statements of the following files in the distribution: ./backend/myasn-scan.perl ./backend/myasn-send.perl ./lib/RIPE/NCC/myASn.pm ./www/syshandler as long as it might be specified in myasn.conf configuration file. Once myasn check out the following symbolic links should be made on frontend server (halfweg.ripe.net) ln -s /home/risops/myasn/www /home/risops/www/ris/myasn ln -s /home/risops/myasn/alzabo/schemas/myasn /var/www/alzabo/schemas/myasn XXX Arife might want to add here comments about ris.rc file she made. 3. Configuring myASn Once myASn is installed the configuration of myasn is done via master configuration file, /home/risops/myasn/etc/myasn.conf It basically consists of line with name = value, where in most cases name is the same as a command line arguement of myasn scripts without leading dashes. For example, one could put risdb-username = myasn which would be similar to issuing myasn-scan --risdb-username myasn There are a number of variables that are common to all myASn components, example values are given: risdb_hostname = 193.0.0.210 Hostname or ip address of the RIS database. risdb_username = myasn Username to use for connecting to RIS database. risdb_password = ticvdkjw Password to go with the username above. myasn_database = myasn Hostname or ip address of the myASn database. myasn_hostname = 193.0.0.210 myasn_username = myasn Username to use for connecting to myASn database. myasn_password = tiablkdfd;akj The password to use to connect to myASn datbase. myasn_port = 3306 Port to use to connect to myASn database. pidfile_dir = /home/risops/myasn/log The directory where all the pid/lockfiles will be created. Must be writable to myasn-scan and myasn-send invoking users. The pid files will be created in the format of: $pidfile_dir/myasn-scan.$rrc.pid $pidfile_dir/myasn-send.pid This option can be overwritten with pidfile option that doesnt do rrc name expansion like shown above. The same rules apply to logfile_dir and logfile variables. logfile_dir = /home/risops/myasn/log The directory where all the logfiles will be stored. Same requirement as above. rrc_list = rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 White-space separated list of the route collectors. Once a new RRC is added it should be added here as well and myasn related tables should be created. XXX Arife more on this? # wait these many seconds for myasn-send loop wait = 900 This one is myasn-send specific. myasn-send will wait this many seconds before starting sending a new serious of alarm notifications by email. # wait these many seconds for myasn-scan loop loop-wait = 300 This is a similar variable for myasn-scan. myasn-scan will wait this many seconds before processing new series of bgp updates. # delay this many seconds before forking next child fork-delay = 30 myasn-scan will wait this many seconds before forking another child process. This is done to desyncronize processing of rrc to avoid peak mysql workloads. To configure the frontend, the Apache's httpd.conf needs the following lines added: <Location /myasn> AuthType Basic AuthName "MyASN Login" AuthUserFile /home/risops/myasn/etc/myasn-passwords Require valid-user SetHandler perl-script PerlHandler HTML::Mason::ApacheHandler PerlSetVar MasonAllowGlobals $User PerlSetVar MasonAutohandlerName autohandler.html </Location> The first section is responsible for authenticating users, and the second one makes sure that the myASn files are handled by Mason. 4. Accounts and users myASn account in standalone version is the same thing as LIR registry in the original LIR portal version. myASn account might have a number of users that share the same alarm configuration and have access to the same information. As a matter of fact myASn doesn't know anything about users, it only cares about the accounts or registries. Usernames are used solely for access authorization purposes and welcome text. As far as user accounts are concerned they are created automatically based on the $User->username and $User->regid global variables. These variables are either initialized by LIR Portal (for LIR Portal version) or by syshandler in the standalone version. In standalone version $User->username and $User->regid are produced by splitting Apache username into username@regid parts. Therefore Apache username alexis@55555 will result in $User->username = 'alexis' and $User->regid = '55555' If myasn account 55555 does not exist yet, it will be created automatically. Therefore to create a new myasn account a new user should be added into /home/risops/myasn/etc/myasn-passwords file. It can be done with htpasswd /home/risops/myasn/etc/myasn-passwords username@accountname password, for example: htpasswd /home/risops/myasn/etc/myasn-passwords alexis@55555 alexis123 will create an account 55555 with username alexis that will have password 123 To change user password the same command as above should be used. XXX - User management, put e-mail template of user request XXX I'm not sure what kind of template I must provide?!? 5. Logging myASn logfiles go into the location specified by --logfile or --logfile-dir options specified either in myasn.conf configuration file or at command line. When myasn-scan is invoked with --logfile-dir, logfile name expansion is being made in a form of: $logfile_dir/myasn-scan.$rrc.log So ig logfile_dir is /home/risops/myasn/log, then for every rrc there will be a separate logfile created. For example for rrc05: /home/risops/myasn/log/myasn-scan.rrc05.log The same applies to --pidfile and --pidfile-dir directives. 6. Backend demon's invokation As mentioned above, two myasn demons are running on weesp.ripe.net (or whatever backend server is in use): myasn-scan myasn-send myasn-scan needs to know to which databases to connect and which credentials to use, location of its logfile and pidfile directory, and loop-wait, fork-delay. All of which is normally specified in myasn.conf file. The only command line myasn-scan should require if myasn.conf is properly setup is: myasn-scan.perl --fork --loop This command tells that myasn-scan should loop, that is keep on waiting on an processing incoming data, and that it should fork a separate process for every rrc. It is important that fork-delay variable is configured, so that not all the processes will be accessing the database exactly at the same time, but with some offset. myasn-send will fork by default so it doesn't require any command line. 7. Maintenance XXX To be developed

2 1

ziya is ris-int from now on.
by Arife Vural 02 Aug '04

02 Aug '04

All in subject.

1 0