January 2005 - Ris-int - mailman.ripe.net

This ticket is getting really urgent
by Henk Uijterwaal 31 Jan '05

31 Jan '05

Ruud, This is the ticket I was talking about... Update of beacon prefixes: Original ticket 107265, created Nov 16 after discussion in the RIS meeting and agreement that James would be the best person to do this. No response in the ticket but told by VOS several times that he'd look at it "soon". Last reminder 110383, Jan 24: again no written response but an oral "this week, I know the deadline is 1/2" last week. No action up until today. The current address block used for these studies will expire today, this sets the deadline. 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 ------------------------------------------------------------------------------ Look here junior, don't you be so happy. And for Heaven's sake, don't you be so sad. (Tom Verlaine)

1 0

We have RIS meeting in 10 min in Fishtank
by Arife Vural 31 Jan '05

31 Jan '05

1 0

Fwd: Announce: BGP::Inspect
by Henk Uijterwaal 31 Jan '05

31 Jan '05

In case you didn't see this... might be of interest for us. Henk >Delivered-To: nanog-outgoing(a)trapdoor.merit.edu >Delivered-To: nanog(a)trapdoor.merit.edu >Delivered-To: nanog(a)segue.merit.edu >Delivered-To: nanog(a)merit.edu >Date: Fri, 28 Jan 2005 10:38:07 -0500 (EST) >From: Manish Karir <mkarir(a)merit.edu> >To: nanog(a)merit.edu >Subject: Announce: BGP::Inspect >Sender: owner-nanog(a)merit.edu >X-Loop: nanog >X-RIPE-Spam-Level: >X-RIPE-Spam-Tests: BAYES_20,WEIRD_PORT >X-RIPE-Spam-Status: U 0.471924 / -1.8 >X-RIPE-Signature: 75fee9f0bc3246c1f95125a5a27825c6 > > > >All, > >Merit Network and the University of Maryland would like to announce the >beta release of a BGP update messages research tool that might be of use >to the NANOG community. The tool is called BGP::Inspect. The goal is to >make the vast quantities of Routeviews data easily accesible to the >network operator and research community. This involves not just allowing >people to query and obtain the update messages, but also providing some >simple analysis and statistics on the data which can help in locating >anomalies and problems. > >At this point we feel that we could really benefit from some feedback from >the community. A beta release of our prototype is available at: >http://weasel.merit.edu:9191/ >This version has been initialized with a limited amount of data. It >currently provides information regarding 5 of the 40 routeview peers, and >only contains data for the time period from Dec 20 - Jan 6. > >The basic interface has been kept simple. There are 2 types of queries >that can be run "Summary Queries" and "Raw Data Analysis". The summary >queries allow users to quickly focus on potential trouble spots(as >observed at the routeview peers). Basic queries include things like most >active ASes, most active prefixes, as well as prefixes that exhibited the >most number of changes in their OriginAS. > >The second type of queries, "Raw Data Analysis" can be used to obtain >information regarding specific ASes or prefixes for a given time range. >A query for a specific AS will return not only the various prefixes >announced by that AS, the times, paths, and communities, but also summary >stats including total number of announcements in that time period and the >number of unique prefixes announced in that time period. A 7 day summary >graph is also returned which summarized the most recent activity as seen >originating from that AS. >A similar query for a specific prefix will return times, >types(announce/withdraw), aspaths and communities from update messages >as well as summary statistics that indicate the min/max/avg AS path length >as seen over the query time interval, the number of originAS changes as >well as the number of unique ASes that announced that prefix. A summary >graph indicating the activity of that prefix over the last 7 days is also >displayed. > >In a lot of ways this tool complements the Search by AS/Prefix tools from >RIPE, BGP Monitor from MIT, and LinkRank from UCLA. The more views from >different vantage points the better. In addition there is a real effort >with BGP::Inspect to provide not simply access to the raw data, but some >simple analysis and summary statistics as well. The hope is that people >no longer need to write custom parsers to be able to extract the >information they need. > >We would appreciate any and all feedback from the NANOG community. In >particular, it would be instructive to us to learn what are some other >"typical" queries that we could add, in addition to the the "Top 20 most >active ASes/Prefixes" and "Top 20 prefixes which have most number of >origin AS changes." What are some other basic questions that researchers >and network operators ask when attempting to analyze problems. > >Please send feedback offlist to: mkarir(a)merit.edu > >thanks >manish karir >-------------------------------------------- ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Look here junior, don't you be so happy. And for Heaven's sake, don't you be so sad. (Tom Verlaine)

1 0

eBay Security Update
by aw-confirm＠ebay.com 29 Jan '05

29 Jan '05

1 0

[ugin@ripn.net: Re: [ris-int] Re: Installation CD for RRC13]
by Arife Vural 26 Jan '05

26 Jan '05

James, Could you please get back to Evgueni? Arife ----- Forwarded message from 'Evgueni Kouskevitch' <ugin(a)ripn.net> ----- From: "'Evgueni Kouskevitch'" <ugin(a)ripn.net> To: James Aldridge <james(a)ripe.net> Subject: Re: [ris-int] Re: Installation CD for RRC13 Date: Wed, 26 Jan 2005 18:03:14 +0300 Cc: Arife Vural <arife(a)ripe.net>, ris-int(a)ripe.net On Tue, Dec 21, 2004 at 06:02:17PM +0300, 'Evgueni Kouskevitch' wrote: > On Fri, Dec 17, 2004 at 02:36:03PM +0100, James Aldridge wrote: > > "'Evgueni Kouskevitch'" wrote: > > > On Tue, Nov 16, 2004 at 02:27:26PM +0100, Arife Vural wrote: > > > > > > > > Hi Evgueni, > > > > > > > > Thanks for getting back to us. There might be a problem at the > > > > installation CD. We will get back to you about it. > > > > > > Hi, > > > > > > do you have any news about the case? > > > > I'm not sure of the exact configuration of the machine. Could you please let > > me know full details of the disk/raid controllers, etc. so I can check that > > this is properly supported by the installation CD. > > Hi, > > - PowerEdge Expandable RAID controller (BIOS H406 Oct 9 2003) > - Three Fujitsu MAP3735NC drives configured as RAID 1 array, as > described in "RIS RRC Migration - Dell PowerEdge 1550, 1750, 2550, 2650" document Hello, James. I am very sorry that this deal is taking so long and we've found ourselves in such a bad situation. Maybe I should try to perform a common Red Hat Linux installation, configure network on the system and provide you access to it. So you'll be able to make all the neccessary configuration remotely. What do you think about it ? > > > > > Regards, > > James > > -- > Evgueni G. Kouskevitch <ugin(a)ripn.net> Russian Institute for > RIPN NOC:+7(095)192-9179 Public Networks > -- Evgueni G. Kouskevitch <ugin(a)ripn.net> Russian Institute for RIPN NOC:+7(095)192-9179 Public Networks ----- End forwarded message -----

1 0

Re: [ris-int] Re: Installation CD for RRC13
by James Aldridge 26 Jan '05

26 Jan '05

"'Evgueni Kouskevitch'" wrote: > On Tue, Nov 16, 2004 at 02:27:26PM +0100, Arife Vural wrote: > > > > Hi Evgueni, > > > > Thanks for getting back to us. There might be a problem at the > > installation CD. We will get back to you about it. > > Hi, > > do you have any news about the case? I'm not sure of the exact configuration of the machine. Could you please let me know full details of the disk/raid controllers, etc. so I can check that this is properly supported by the installation CD. Regards, James

2 2

New beacon prefixes and routing experiments
by Lorenzo Colitti 25 Jan '05

25 Jan '05

Hi, at the RIS meeting a couple of months ago I asked if it would make sense to reserve one or more IPv4 beacon prefixes for my fancy beacon ("as-set stuffing") experiments. However, there are very few prefixes left out of the new /19 that has been assigned to beacons. The new scheme envisages a /24 beacon prefix and a /24 anchor prefix for each RRC. So for the 13 currently active RRCs we use 26 prefixes out of the 32. But the current list of beacon prefix assignments ( http://www.ripe.net/projects/ris/docs/beaconlist.html ) lists two more beacons, one for K-root anycast failover, and one for anycast server research (requested by hitesh(a)cs.cornell.edu). If these were to need an anchor prefix each, we would be up to 30 prefixes out of the 32 we have. Therefore: - If possible, I would like to reserve two prefixes for as-set stuffing experiments - I think we should consider requesting more address space for beacons. With this arrangement, the address space we have would be completely maxed out from the start. So if, for example, the Dubai RRC were ever to come online, we wouldn't have a prefix to announce there. Or if another researcher were to request a custom beacon, we wouldn't have one to give them. Thoughts? Cheers, Lorenzo

1 0

Update of beacon prefixes (Ticket 107265)
by Henk Uijterwaal 24 Jan '05

24 Jan '05

Folks, I do not want to create panic, but this ticket has been open for more than 2 months and the deadline for returning the present block is approaching very rapidly. Is there any chance this can be done sometime really soon? 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 ------------------------------------------------------------------------------ Look here junior, don't you be so happy. And for Heaven's sake, don't you be so sad. (Tom Verlaine)

1 0

Fwd: Cross-console for RIS box - F root in NYC
by Joe Abley 20 Jan '05

20 Jan '05

Arife, Can you confirm that your box in New York has two serial ports available, one to talk to our console and one to act as RIS console? Joe Begin forwarded message: > From: Joao Damas <Joao_Damas(a)isc.org> > Date: 18 January 2005 09:38:42 EST > To: Systems Operations <ops-workers(a)isc.org> > Subject: Fwd: Cross-console for RIS box - F root in NYC > > RIPE are agreeable to a cross console arrangement if we can get the > cables in place. OUr username on their box will be isc, and theirs on > ours will be risops, as per below > > Joao > > Begin forwarded message: > >> From: Joao Damas <Joao_Damas(a)isc.org> >> Date: 17 January, 2005 12:39:28 CET >> To: Arife Vural <arife(a)ripe.net> >> Cc: ris-int(a)ripe.net, andrei(a)ripe.net >> Subject: Re: [henk(a)ripe.net: Fwd: Re: [Fwd: Cross-console for RIS box >> - F root in NYC]] >> >> >> On 17 Jan, 2005, at 11:04, Arife Vural wrote: >> >>> >>> Hi Joao, >>> >>> Sorry for the late reply. >>> >>> That sounds good. Do you think you can do the cabling over there? >> >> I think we can get telehouse to do it for us, yes. >> >>> I ask OPS >>> to create an account on RIS box, and you can get the console through >>> this user. >>> As username, is isc OK, or would you like to have something else? >> >> isc is fine for us. >> >>> For ris, I suggest you to use risops. >>> >> >> shall do >> I will let you know as we get telehouse to schedule this >> >> >> Joao >> >

3 12

RIS stuff in TTM CVS repo
by Mark Santcroos 19 Jan '05

19 Jan '05

Hi all, I propose to move the above files to the /ncc/cvsroot repo. Please let me know if I can be of any help in doing that. Thanks Mark -- RIPE NCC - Delft University of Technology - The FreeBSD Project marks(a)ripe.net - m.a.santcroos(a)ewi.tudelft.nl - marks(a)freebsd.org

4 6