- Ris-int - mailman.ripe.net

[ripe.net #110383] Re: [ris-int] Re: Fwd: 195.80.224.0 - 195.80.239.255 "RIPE NCC Route Flap Dampening,and BGP Beacon Studies"
by James Aldridge 04 Feb '05

04 Feb '05

Henk Uijterwaal wrote: > At 15:14 04/02/2005, Arife Vural wrote: > > >It would be nice if James update RIPE DB, after finish up activating > >new Beacon prefix. > > > >I think we should delete those entries. > > I believe that the new prefixes have been activated, Indeed they have. The beacon configuration is now moved outside cron (so all the RRCs can now share a single risops crontab file). The new beacons work as follows: The /usr/local/ris/etc/bgp-beacon /bin/sh script is run every 5 minutes from risops' crontab. Whether there's anything to do at a particular run is governed by the (RRC-specific) configuration file /usr/local/ris/etc/bgp-beacon.def (a files which is sourced by the bgp-beacon script). As an example, rrc03's file looks like the following: # $Id: rrc03,v 1.2 2005/01/31 13:10:36 root Exp $ # Beacon definitions for rrc03 - AMS-IX, etc. nexthop=195.69.144.69 beacons="1 2" beacon_1_prefix=84.205.67.0/24 beacon_1_on="00:00:00 04:00:00 08:00:00 12:00:00 16:00:00 20:00:00" beacon_1_off="02:00:00 06:00:00 10:00:00 14:00:00 18:00:00 22:00:00" beacon_2_prefix=84.205.72.0/24 beacon_2_on="00:00:00 04:00:00 08:00:00 12:00:00 16:00:00 20:00:00" beacon_2_off="02:00:00 06:00:00 10:00:00 14:00:00 18:00:00 22:00:00" I hope that that's fairly self explanatory. Files are mastered on the risadmin server (where they're under RCS control) and are included in the daily sync to the RRCs. > all that is left to > be done is the route object and the webpage. The various IRR objects have been created/updated/removed as appropriate (on 31st January): route-set: AS12654:RS-RIS descr: RIPE NCC RIS Project members: 84.205.64.0/24 members: 84.205.65.0/24 members: 84.205.66.0/24 members: 84.205.67.0/24 members: 84.205.68.0/24 members: 84.205.69.0/24 members: 84.205.70.0/24 members: 84.205.71.0/24 members: 84.205.72.0/24 members: 84.205.73.0/24 members: 84.205.74.0/24 members: 84.205.75.0/24 members: 84.205.76.0/24 members: 84.205.77.0/24 members: 84.205.78.0/24 members: 84.205.79.0/24 members: 84.205.80.0/24 members: 84.205.81.0/24 members: 84.205.82.0/24 members: 84.205.83.0/24 members: 84.205.84.0/24 members: 84.205.85.0/24 members: 84.205.86.0/24 members: 84.205.87.0/24 members: 84.205.88.0/24 members: 84.205.89.0/24 members: 84.205.90.0/24 members: 84.205.91.0/24 members: 84.205.92.0/24 members: 84.205.93.0/24 members: 84.205.94.0/24 members: 84.205.95.0/24 members: 86.192.0.0/16 members: 86.255.248.0/21 members: 87.192.0.0/16 members: 87.255.248.0/21 members: 88.192.0.0/16 members: 88.255.248.0/21 remarks: The RIPE NCC RIS Project announces a small number of remarks: prefixes at various times for experimental purposes. remarks: Very little traffic is expected to be directed to or remarks: sourced from these prefixes. Any such traffic will only remarks: be for reachability tests. tech-c: RISM-RIPE admin-c: HU266-RIPE mnt-by: RIPE-NCC-RIS-MNT mnt-lower: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20040218 changed: risops(a)ripe.net 20040402 changed: risops(a)ripe.net 20040820 changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.64.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc00 - RIPE NCC origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.65.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc01 - LINX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.66.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc02 - SFINX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.67.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc03 - AMS-IX, NL-IX, GN-IX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.68.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc04 - CIXP origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.69.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc05 - VIX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.70.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc06 - DIX-IE origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.71.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc07 - NETNOD origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.72.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix descr: For anycast failover analysis at LINX and AMS-IX descr: (replaces 195.80.233.0/24) origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.73.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix descr: For anycast failover analysis at LINX, SFINX, VIX, DIX-IE and NYIIX descr: (replaces 195.80.238.0/24) origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.74.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc10 - MIX-IT origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.75.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc11 - NYIIX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.76.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc12 - DECIX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.77.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc13 - MSK-IX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.78.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix @ rrc14 - PAIX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.79.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.80.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc00 - RIPE NCC origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.81.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc01 - LINX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.82.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc02 - SFINX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.83.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc03 - AMS-IX, NL-IX, GN-IX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.84.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc04 - CIXP origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.85.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc05 - VIX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.86.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc06 - DIX-IE origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.87.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc07 - NETNOD origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.88.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.89.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.90.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc10 - MIX-IT origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.91.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc11 - NYIIX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.92.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc12 - DECIX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.93.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc13 - MSK-IX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.94.0/24 descr: RIPE-NCC-RIS BGP Anchor Prefix @ rrc14 - PAIX origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE route: 84.205.95.0/24 descr: RIPE-NCC-RIS BGP Beacon Prefix origin: AS12654 mnt-by: RIPE-NCC-RIS-MNT changed: risops(a)ripe.net 20050131 source: RIPE (those that don't include "@ rrc" in the descr field are currently unused) and the web page http://www.ripe.net/projects/ris/docs/beaconlist.html has been updated I guess that the old /20 block of addresses can now be returned to RS. James -- James Aldridge, Systems & Network Engineer, RIPE NCC Operations Group Tel: +31 20 535 4421 / Fax: +31 20 535 4445 / GSM: +31 6 1092 2791

2 1

Re: [ris-int] Re: Fwd: 195.80.224.0 - 195.80.239.255 "RIPE NCC Route Flap Dampening,and BGP Beacon Studies"
by Rene Wilhelm 04 Feb '05

04 Feb '05

>>The guy seems to be asking for *adding* objects for the *old* >>beacon prefixes to the RIPE DB: > OK, let me rephrase this :-) Can we check if we have the correct route > objects for what is currently announced _and_ that nothing of the old > beacons is announced anymore? (ris)whois is your friend :) x27$ whois -T route -M 84.205.64.0/19 | grep route | wc 32 64 928 i.e. 32 route objects in the DB, starting 84.205.64.0/24 and ending with 84.205.95.0/24 x27$ whois -h riswhois -F -M 84.205.64.0/19 |grep 12654 12654 84.205.72.0/24 49 12654 84.205.80.0/24 54 12654 84.205.81.0/24 49 12654 84.205.82.0/24 54 12654 84.205.83.0/24 45 12654 84.205.84.0/24 1 12654 84.205.85.0/24 64 12654 84.205.87.0/24 60 12654 84.205.90.0/24 10 12654 84.205.91.0/24 52 12654 84.205.92.0/24 72 RISwhois only sees the anchor prefixes, as the beacons are always withdrawn at the times of the bview dumps The anchor prefix 84.205.86.0/24 from rrc06, japan, is not seen by any other RRC; probably does not get transit from any of the DIX-IE peers x27$ whois -h riswhois -M 195.80.224.0/20 % 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 % No entries found The true ON/OFF Beacons were never seen, so their absence from riswhois doesn't say much on the status of these, but the 195.80.239.0/24 anchor prefix and the anycast simulation 195.80.233.0/24 prefix from rrc01 were in RISwhois before and have now disappeared. -- Rene

1 0

Re: [ris-int] Re: Fwd: 195.80.224.0 - 195.80.239.255 "RIPE NCC Route Flap Dampening,and BGP Beacon Studies"
by Rene Wilhelm 04 Feb '05

04 Feb '05

> I think we should delete those entries. > > A. The guy seems to be asking for *adding* objects for the *old* beacon prefixes to the RIPE DB: >> >Hi Henk >> > >> >Could you please update the RIPE database with a valide ROUTE-Object for >> >the network: >> > >> >195.80.238.0/24 since at least Fri Feb 13 01:47:26 2004 >> >195.80.239.0/24 since at least Fri Feb 13 01:47:26 2004 >> > >> >Cheers >> > >> >M. However, as they are no longer announced, I'd say it's ok for those route objects to not be there. If the old address space has been returned to hostmasters, the old inetnum objects perhaps should be deleted too. But it's been toooo long ago since I had the LIR training course to know the details :-) -- Rene

2 1

Fwd: 195.80.224.0 - 195.80.239.255 "RIPE NCC Route Flap Dampening,and BGP Beacon Studies"
by Henk Uijterwaal 04 Feb '05

04 Feb '05

I'm not really sure where this belongs, but can this be done? Henk >X-Recipient: <henk(a)ripe.net> >Date: Wed, 02 Feb 2005 10:04:05 +0100 >From: Marco Huggenberger <huggenberger(a)init7.net> >Organization: Init Seven AG - http://www.init7.net >User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) >X-Accept-Language: de-DE, de, en-us, en >To: henk(a)ripe.net >Subject: 195.80.224.0 - 195.80.239.255 "RIPE NCC Route Flap Dampening,and > BGP Beacon Studies" >X-Enigmail-Version: 0.89.6.0 >X-Enigmail-Supports: pgp-inline, pgp-mime >X-RIPE-Spam-Level: >X-RIPE-Spam-Tests: BAYES_00 >X-RIPE-Spam-Status: N 0.069753 / -2.6 >X-RIPE-Signature: f831cc4c6f1de53be4d618b2c36c28e0 > >Hi Henk > >Could you please update the RIPE database with a valide ROUTE-Object for >the network: > >195.80.238.0/24 since at least Fri Feb 13 01:47:26 2004 >195.80.239.0/24 since at least Fri Feb 13 01:47:26 2004 > >Cheers > >M. ------------------------------------------------------------------------------ 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)

2 2

[ops: 110383] Update of beacon prefixes
by Henk Uijterwaal 04 Feb '05

04 Feb '05

James, You (and I) overlooked this one: >http://www.ris.ripe.net/beacons/200502/beacon-matrix-20050203.shtml 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

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