January 1999 - Test - lists.nanog.org

OUTAGE/WEATHER: severe winter weather and mci worldcom
by Sean Donelan 04 Jan '99

04 Jan '99

A summary of few of the larger infrastructure issues in the last few days January 3-4 (18+ hours) MCI Worldcom had water problems in a New York/New Jersey office (the reports haven't clearly identified the location) damaging some unspecified equipment. At least two OC48s are out of service. See next issue. January 1-3 Severe winter weather across the midwest to the east coast. Sporadic power outages in multiple states affecting 450,000 people. 39 deaths. One news station reported 7 counties in central Illinois lost telephone service. Travel conditions have greatly increased repair response times in affected areas. If last year is a guide, major problems won't surface until the weather warms up a bit. Flooding and heavy equipment use caused several post-winter storm outages last winter. I did read the other thread. What the rough consensus was wasn't clear to me, so I'm going ahead with this message. -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation

1 0

Re: What is NANOG used for? (Was Re: Exodus?)
by Alex Bligh 04 Jan '99

04 Jan '99

Randy Bush (randy(a)psg.com) said: > another way to look at it: So much more verbose than "How can I configure my router to do that?"... :-p -- Alex Bligh GX Networks (formerly Xara Networks)

1 0

What is an "Internet" outage?
by Michael Dillon 04 Jan '99

04 Jan '99

On Sun, 3 Jan 1999, Randy Bush wrote: > there has been an interesting discussion on sean's idig list regarding > criteria to warrant formal recording. it is an interesting issue. we > think we know what we mean by a major outage until we try to formally This probably doesn't help much in nailing it down.... An outage is major if the general public and the press would perceive it as an Internet outage rather than a single provider outage. A multi-provider outage counts. So does a single provider outage that affects a large enough geographic area that the public would perceive it as multiple outages, i.e. the Internet is down in Boston and New York and all over the place. Even a single provider outage at a backbone that causes outages at several ISP's in a single city would be an "Internet" outage, especially if the backbone were to be one of the dialup modem suppliers to nationals like Earthlink, AOL, et al. I guess the point I am trying to make is to start from public perceptions since we are talking about mainly the reporting of an analysis for publicly known outages. If a SONET ring fails over then there is no publicly known outage. But when it starts to affect multiple points then the public takes note and it is a significant outage that we need to learn from. Could be multiple geographical points, multiple circuits, or multiple providers. -- Michael Dillon - E-mail: michael(a)memra.com Check the website for my Internet World articles - http://www.memra.com

1 0

Problems @ Exodus?
by Lawrence A. Deleski 04 Jan '99

04 Jan '99

I have been having problems getting to (and keeping connections with) certain Exodus clients, such as HotBot and GeoCities. Anyone else noticed this? Traceroutes seem to be blowing up in the same place... Find route to: www.geocities.com. (209.1.224.12), Max 30 hops, 40 byte packets 1 ldeleski-isdn.cisco.com. (171.68.18.89): 11 ms 5 ms 5 ms 2 171.70.196.1 (171.70.196.1): 121 ms 116 ms 130 ms 3 171.70.192.131 (171.70.192.131): 118 ms 117 ms 117 ms 4 gaza-gw2.cisco.com. (171.68.0.91): 118 ms 117 ms 117 ms 5 sj-wall-1.cisco.com. (198.92.1.137): 118 ms 117 ms 117 ms 6 barrnet-gw.cisco.com. (192.31.7.37): 133 ms 119 ms 117 ms 7 s2-1-1.paloalto-cr18.bbnplanet.net. (131.119.26.9): 128 ms 121 ms 145 ms 8 p3-2.paloalto-nbr2.bbnplanet.net. (4.0.3.85): 120 ms 118 ms 125 ms 9 p9-0-0.paloalto-br1.bbnplanet.net. (4.0.1.221): 122 ms 127 ms 119 ms 10 ibr02-h8-1-0.sntc01.exodus.net. (209.1.169.233): 134 ms 121 ms 120 ms 11 dcr02-f2-1-0.sntc01.exodus.net. (209.185.9.37): 230 ms 137 ms 194 ms 12 209.1.217.19 (209.1.217.19): 123 ms 122 ms 122 ms 13 * * * 14 [more of the same] Find route to: www.hotbot.com. (209.185.151.128), Max 30 hops, 40 byte packets 1 ldeleski-isdn.cisco.com. (171.68.18.89): 5 ms 5 ms 5 ms 2 171.70.196.1 (171.70.196.1): 118 ms 118 ms 116 ms 3 171.70.192.130 (171.70.192.130): 119 ms 117 ms 117 ms 4 gaza-gw1.cisco.com. (171.68.0.44): 118 ms 117 ms 118 ms 5 sj-wall-1.cisco.com. (198.92.1.137): 121 ms 118 ms 117 ms 6 barrnet-gw.cisco.com. (192.31.7.37): 119 ms 120 ms 117 ms 7 s2-1-1.paloalto-cr18.bbnplanet.net. (131.119.26.9): 123 ms 119 ms 125 ms 8 p3-2.paloalto-nbr2.bbnplanet.net. (4.0.3.85): 120 ms 119 ms 118 ms 9 p9-0-0.paloalto-br1.bbnplanet.net. (4.0.1.221): 121 ms 120 ms 119 ms 10 ibr02-h8-1-0.sntc01.exodus.net. (209.1.169.233): 122 ms 121 ms 120 ms 11 dcr02-f10-1-0.sntc01.exodus.net. (209.1.169.145): 123 ms 121 ms 127 ms 12 209.1.231.166 (209.1.231.166): 367 ms 300 ms 229 ms 13 209.185.255.195 (209.185.255.195): 195 ms 207 ms 216 ms 14 * * * 15 * * [...yadda yadda...] Larry Deleski ldeleski(a)cisco.com

6 9

Re: What is NANOG used for? (Was Re: Exodus?)
by Dave Crocker 03 Jan '99

03 Jan '99

At 04:11 PM 1/3/99 -0800, Randy Bush wrote: >> For all the topics that are regarded as being on-topic, there's a common >> aspect: they affect multiple providers. Telco issues. Tool issues. Vendor ... >another way to look at it: perhaps a web page which 'charters' the nanog list and defines the scope/nature of its intended discussions will help to avoid future misunderstandings? perhaps a version of the text of your note would be an excellent draft for that charter? d/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Dave Crocker Tel: +60 (19) 3299 445 <mailto:dcrocker@brandenburg.com> Post Office Box 296, U.P.M. Serdang, Selangor 43400 MALAYSIA Brandenburg Consulting <http://www.brandenburg.com> Tel: +1 (408) 246 8253 Fax: +1(408)273 6464 675 Spruce Dr., Sunnyvale, CA 94086 USA

2 1

Re: What is NANOG used for? (Was Re: Exodus?)
by John Hawkinson 03 Jan '99

03 Jan '99

It it was appropriate for nsr(a)merit.edu, then it's no good for NANOG. Of course, maybe the real solution is we should all go back to using regional-techs. If you have no idea what I'm talking about, well, perhaps it's for the best. If you do know what I'm talking about and think I'm joking, well, you might be wrong. --jhawk

1 0

Re: Problems @ Exodus?
by Lawrence A. Deleski 03 Jan '99

03 Jan '99

Stephen, Thanks for the snide tone of your reply. It was just what I was looking for... Or...I was attempting to discover if I was the only one seeing these problems, which does sometimes happen inside of Cisco's firewall(s). With all of the energy (and bandwidth) that has been devoted to sending replies like yours, it's no wonder the on-topic subject seems to come up more often than not. nanog is an operational list, so I attempted to locate a source of information for something that was not operating. I was indeed attempting to use it for something other than spam hate-mail, flaming, and the occasional bout of an inflated ego (or two). Also, I'm not all that interested in what you find "interesting" or not, in fact, I am surprised you bothered to respond at all, given your profound lack of interest and all... And yes, I sent an email to Rob. The Exodus NOC is not all that...well, you know. Larry ---------- >From: Stephen Stuart <stuart(a)tech.org> >To: "Lawrence A. Deleski" <lad(a)inficad.com> >Subject: Re: Problems @ Exodus? >Date: Sun, Jan 03, 1999, 1:09 PM > >Not until you mentioned it; I don't consider the content published by >GeoCities or HotBot to be interesting at all, but I did a couple >traceroutes special just for you and I can't reach either. > >Have you considered notifying the Exodus NOC? Or did you just want to >share the fact that you can't reach Geocities and HotBot with a few >thousand people to see how many agree? > >Stephen >- ----- >Stephen Stuart ><stuart(a)tech.org> > >

1 0

Re: What is NANOG used for? (Was Re: Exodus?)
by Bill Woodcock 03 Jan '99

03 Jan '99

I'd suggest restricting discussion of single-provider outages to the IPNMOO or IPN (Inter-Provider Notification) mailing lists. -Bill

1 0

The Cidr Report
by Tony Bates 01 Jan '99

01 Jan '99

This is an auto-generated mail on Fri Jan 1 12:00:00 PST 1999 It is not checked before it leaves my workstation. However, hopefully you will find this report interesting and will take the time to look through this to see if you can improve the amount of aggregation you perform. The report is split into sections: 0) General Status List the route table history for the last week, list any possibly bogus routes seen and give some status on ASes. 1) Gains by aggregating at the origin AS level This lists the "Top 30" players who if they decided to aggregate their announced classful prefixes at the origin AS level could make a significant difference in the reduction of the current size of the Internet routing table. This calculation does not take into account the inclusion of holes when forming an aggregate so it is possible even larger reduction should be possible. 2) Weekly Delta A summary of the last weeks changes in terms of withdrawn and added routes. Please note that this is only a snapshot but does give some indication of ASes participating in CIDR. Clearly, it is generally a good thing to see a large amont of withdrawls. 3) Interesting aggregates Interesting here means not an aggregate made as a set of classful routes. Thanks to xara.net for giving me access to their routing tables once a day. Please send any comments about this report directly to me. Check http://www.employees.org/~tbates/cidr-report.html for a daily update of this report. ------------------------------------------------------------------------------ CIDR REPORT for 01Jan99 0) General Status Table History ------------- Date Prefixes 251298 54839 261298 54849 271298 54731 281298 54848 291298 54977 301298 55085 311298 55006 010199 55011 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- AS Summary ---------- Number of ASes in routing system: 4378 Number of ASes announcing only one prefix: 2165 (1152 cidr, 1013 classful) Largest number of cidr routes: 351 announced by AS3561 Largest number of classful routes: 1008 announced by AS701 1) Gains by aggregating at the origin AS level --- 01Jan99 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 392 146 246 62.8% BCnet Backbone AS3749 228 75 153 67.1% TECNET AS2493 327 180 147 45.0% iSTAR Internet, Inc. AS701 1008 864 144 14.3% Alternet AS1785 541 403 138 25.5% NYSERNet Backbone AS174 671 548 123 18.3% Performance Systems International AS5668 132 36 96 72.7% Century Telephone Inc. AS4200 190 97 93 48.9% AGIS (Apex Global Information Ser AS4755 148 66 82 55.4% Videsh Sanchar Nigam Ltd. India AS1267 107 29 78 72.9% IUNET-AS AS4293 208 136 72 34.6% IMCI AS549 220 154 66 30.0% ONet Backbone AS4740 382 321 61 16.0% Ozemail Pty Ltd (ASN-OZEMAIL) AS8517 129 72 57 44.2% UNKNOWN AS1221 378 321 57 15.1% AARNET-AS AS7046 248 192 56 22.6% UUNET-CUSTOMER AS7545 115 65 50 43.5% TPG Internet Pty Ltd AS1239 533 484 49 9.2% SprintLink Backbone AS10928 93 44 49 52.7% UNKNOWN AS72 88 40 48 54.5% Schlumberger Information Network AS7657 138 93 45 32.6% The Internet Group Limited AS7496 73 28 45 61.6% Power Up AS577 208 163 45 21.6% Bell Canada Backbone AS852 174 132 42 24.1% AGT Advance Communication AS719 450 408 42 9.3% LANLINK-AS AS3221 84 42 42 50.0% RIPE-ASNBLOCK4 AS803 71 35 36 50.7% SaskNet Backbone AS7122 109 75 34 31.2% MTS ADVANCED Network Policy AS6897 46 14 32 69.6% RIPE-ASNBLOCK6 AS6332 100 69 31 31.0% TELNOR For the rest of the previous weeks gain information please see http://www.employees.org:80/~tbates/cidr-report.html 2) Weekly Delta Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report 3) Interesting aggregates Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report

1 0