- Test - lists.nanog.org

http://www.above.net/html/pr_052499_paix.html
by Sanjay Dani 24 May '99

24 May '99

Shouldn't be reading press releases, but.. I'm having a hard time reconciling an ISP owned exchange that claims to continue to be neutral. Interested in hearing what imapct other operators see on this exchange. Sanjay. PS. I'm a happy PAIX customer and a happy above.net peer. No gripes.

2 1

Looking for colo system integrator in Chicago
by Hank Nussbacher 24 May '99

24 May '99

Perhaps a bit off-topic and I apologize in advance. I am looking for a colo system integrator in the Chicago area (preferrably a Cisco Gold Partner). Please reply directly to me. Thanks, Hank Nussbacher

1 0

Re: URGENT: NON-OP StarWars Details.
by Craig A. Haney 24 May '99

24 May '99

> > BTW, does anyone know an Avi Fredman? ;) this is him -> http://seamless.kludge.net/nanog/14/jpg/19981110-02.jpg -craig

3 2

URGENT: NON-OP StarWars Details.
by John M. Brown 23 May '99

23 May '99

Ok, All those that wish to goto this movie will meet at 8:30pm in the front lobby of the Hilton Hotel. The Hotel will shuttle us over and back to the Movie. The BUS can take 11 (eleven) people. I have a car and can take three people. Directions will be available at the meet time/point. I am going to go and purchase tickets now. I am front funding 15 tickets. Each ticket is 6.50 a piece. Movie starts at 10:00 PM and will run for 2.5 hours. Movie is at Cinemark Movies 17 (The New One) in Springfield, OR.... jmbrown

2 1

FGC Hospitality Suite at NANOG Monday Evening
by Alan Hannan 23 May '99

23 May '99

Following the "Beer-n-Gear", FGC [Frontier GlobalCenter] is hosting a hospitality suite on the 12th floor of the Eugene, OR, Hilton. Food, Beer, Wine, Network Diagrams, Conversation. Attendees of NANOG are cordially invited. -alan ------------------------ = ------------------------ PLACE: Eugene Hilton Vistas 2 (room) 12th Floor DATE: Monday, May 24 TIME: 7:30p - ------------------------ = ------------------------

1 0

Non-Operational. NANOG Star Wars
by John M. Brown 23 May '99

23 May '99

So I propose that a group of us go see Star Wars on Sunday nite. If you are interested drop some email. Of course I wonder what Eugene, OR has for movie places??????? I can see it now. 50, 80 or how ever many go, NANOG shirted people showing up at the theater at once! :) :) :) :) jmbrown

3 3

Re: exodus?
by Rishi Singh 22 May '99

22 May '99

At 03:11 PM 5/21/99 -0600, you wrote: >Wow, look at how old the message is that you replied to, it's 10/29/98 -- >did you just receive this or what? > >On Fri, 21 May 1999, Rishi Singh wrote: > >> >>At 16:09 -0700 10/29/98, John Gonzalez/netMDC admin wrote: >>>Anybody else have any problems with exodus, or is it just me? >>> >>>traceroute to beta.sierra.com (209.67.71.106), 30 hops max, 40 byte >>>packets My apologies to the list. I was sending some email dealing with Exodus from this list to my account at work and accidentally left the cc: header in one of them. I am not having any problems with Exodus, so ignore the email. Thank you :-). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ <o> The definition of insanity is to keep doing the same thing and <o> expect different results. <o> Rishi M. Singh - Sysadmin & Network "Cleaner" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

Re: NYC FIBER CUT
by Sean Donelan 21 May '99

21 May '99

alan(a)globalcenter.NET (Alan Hannan) writes: > However, for those who have subscribed to nanog for more than 3 > years, nanog has traditionally been useful to discuss operational > issues, where issue is defined as a concept or problem. > > Real time issues are generally helped little by nanog discussions. I agree 100%. Unfortunately, unlike Alan, I've found nanog discussions are very good at fixing 'real time issues' and not so good at fixing long-term operational issues. Carriers should be the ones who first notify their customers about problems. In theory, there should be no way I could know and post about a problem before a carrier monitoring its own facilities. Likewise, reporting a routing loop problem to a carrier should result in its repair without the need to post about it on a public mailing list. After all, it affects them whether reported by a customer or a non-customer. Most of the reasons why I post problems have their root-causes in some very old operational problems. Heck, the routing loop Alan mentioned seems to have been aggravated by a Cisco IOS bug (or at least similar to a bug) dating back to the days when Alan was still a network tech in Nebraska. How about this as a long-term operational issue, defined as a concept or problem: why are we still discussing the same issues three years later? What makes them so difficult to fix? -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation

2 1

The Cidr Report
by Tony Bates 21 May '99

21 May '99

This is an auto-generated mail on Fri May 21 12:00:00 PDT 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 21May99 0) General Status Table History ------------- Date Prefixes 140599 59083 150599 59128 160599 59127 170599 59193 180599 59298 190599 59365 200599 59432 210599 59570 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- *** Bogus 221.43.160.0/19 from AS12323 AS Summary ---------- Number of ASes in routing system: 5001 Number of ASes announcing only one prefix: 2569 (1395 cidr, 1174 classful) Largest number of cidr routes: 400 announced by AS701 Largest number of classful routes: 810 announced by AS701 1) Gains by aggregating at the origin AS level --- 21May99 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 354 144 210 59.3% BCnet Backbone AS4293 270 165 105 38.9% IMCI AS174 595 497 98 16.5% Performance Systems International AS4755 175 86 89 50.9% Videsh Sanchar Nigam Ltd. India AS2493 209 124 85 40.7% iSTAR Internet, Inc. AS577 254 175 79 31.1% Bell Canada Backbone AS3749 141 64 77 54.6% TECNET AS4200 174 98 76 43.7% AGIS (Apex Global Information Ser AS1267 94 24 70 74.5% IUNET-AS AS7496 99 30 69 69.7% Power Up AS1785 384 321 63 16.4% NYSERNet Backbone AS7545 111 49 62 55.9% TPG Internet Pty Ltd AS7122 139 78 61 43.9% MTS ADVANCED Network Policy AS1221 458 397 61 13.3% TELSTRA-AS AS9269 68 9 59 86.8% Hong Kong CTI AS10928 111 54 57 51.4% UNKNOWN AS7657 170 114 56 32.9% The Internet Group Limited AS72 94 39 55 58.5% Schlumberger Information Network AS4740 329 274 55 16.7% Ozemail Pty Ltd (ASN-OZEMAIL) AS719 475 421 54 11.4% LANLINK autonomous system AS1239 525 471 54 10.3% SprintLink Backbone AS7046 251 205 46 18.3% UUNET-CUSTOMER AS3737 111 73 38 34.2% PenTeleData Inc. (ASN-PTD) AS803 73 37 36 49.3% SaskNet Backbone AS1 499 464 35 7.0% BBNPLANET AS4307 32 1 31 96.9% SVINET-1 AS3549 132 101 31 23.5% Frontier GlobalCenter AS2907 208 177 31 14.9% SINET AS11515 32 1 31 96.9% UNKNOWN AS10479 36 5 31 86.1% ITESM-Rectoria Zona Norte 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

Re: NYC FIBER CUT
by Alan Hannan 21 May '99

21 May '99

> > > The reason Sean was beaten in reporting this cut was, after he > > > got off the backhoe, he couldn't find a working NoNuts payphone > > > to logon & file his report... > > > > Either that, or he finally figured out that NANOG was not a > > good place to report fiber outages or routing loops. > > Yep, NANOG is just not the place to report anything bordering on > operational material. Long live SPAMOG. "When did you stop beating your wife?" Sure, real time updates on other people's network problems are less despicable than discussions on spam or smurfing. However, for those who have subscribed to nanog for more than 3 years, nanog has traditionally been useful to discuss operational issues, where issue is defined as a concept or problem. Real time issues are generally helped little by nanog discussions. <sarcasm> I'm looking forward to all of the real time network health and T1 cut updates at next week's NANOG conference. </sarcasm> -alan

1 0