June 1997 - NANOG - lists.nanog.org

Re: MCI outages (summary)
by James A. Farrar 27 Jun '97

27 Jun '97

At 02:32 AM 6/26/97 GMT, William Allen Simpson wrote: >To summarize private reports, MCI NOC lost a fair number of its top >technical staff when they "consolidated" their customer oriented NOCs >into a single unit last year. Now, the folks answering the phone aren't >well trained in Internet; instead they are telco oriented. I noticed >that, too. > > >> ... we don't do >>maintenance in the middle of a sunday afternoon, unless of >>course, you were in australia at the time. >> >That explains why it took half a day to fix your routing problem. >Maintenance shift must come on duty around 10 pm EDT, eh? > border1.hsn#sh clock 20:47:57.710 EDT Thu Jun 26 1997 border1.hsn uptime is 4 days, 4 hours, 39 minutes >And, of course, you've seen the note that you had a router down in >Houston at about those times. Must be official policy not to "admit" >outages. > MCI has an outage list that one may subscribe to if they wish to be notified of events that may affect the Internet community. You should inquire with your service provider about that, thanks. > 4) traceroutes clearly showed that it was an MCI problem. Please forward the trace route in order to further assist you. > > 5) call MCI NOC with information. > > 6) get shrugged off with a recommendation that I send my problem to > trouble(a)mci.com. This would be amazing if it were not so incredibly > stupid, since it was my inability to get my email that brought the > problem to my attention. > <trouble(a)mci.net> would actually be the correct address should you wish to provide some information, thank you. > >>you expect our >>front line noc to know you by name? > >Goodness gracious, while that personal touch can be pleasant, it is not >required. But, I do expect them to have an idea what the IP addresses >of their own routers are, and not have to go on hold to find out about >traceroutes.... > Perhaps you should ensure you are actually calling MCI's NOC, thanks. > >WSimpson(a)UMich.edu > Key fingerprint = 17 40 5E 67 15 6F 31 26 DD 0D B9 9B 6A 15 2C 32 >BSimpson(a)MorningStar.com > Key fingerprint = 2E 07 23 03 C5 62 70 D3 59 B1 4F 5E 1D C2 C1 A2 > jim Regards, Jim Farrar MCI Internet Operations

1 0

Re: PSI woes
by James A. Farrar 27 Jun '97

27 Jun '97

At 03:01 AM 6/26/97 GMT, William Allen Simpson wrote: >> From: dlr(a)bungi.com (Dave Rand) >> Is anyone else having routing problems with PSI? >> >I don't talk directly to PSI, but Morningstar/Ascend does, and I see the >peering between MCI and PSI drop for hours on a regular basis. I find >that the "host unreachable" comes from either #5 or #7 below: > Interesting sir, perhaps you could share what is considered "a regular basis"? Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State 206.157.77.50 4 174 442930 1122979 77754087 0 0 2w6d I will tell you that some /24 announcements are flapping however, I will not waste the time of the individuals on this list to get into that under this forum. Again, if you wish to discuss your concerns offline, my offer to assist you is still open however, you haven't offered much data at this point to be of use. I have not received your source and destination addresses of reported trouble nor any offline communication as of yet for that matter. > 5: 192.203.195.5 cpe3-fddi-1.WillowSprings.mci.net. (109 ms) (109 ms) (107 ms) > 6: 166.48.23.253 bordercore2-hssi1-0.WillowSprings.mci.net. (190 ms) (136 ms) (134 ms) > 7: 204.70.4.9 core3.Atlanta.mci.net. (420 ms) (501 ms) (418 ms) > 8: 206.157.77.50 ast-psi-nap.Atlanta.mci.net. (199 ms) (208 ms) (301 ms) > 9: 38.1.2.5 se2.sc.psi.net. (160 ms) (169 ms) (219 ms) > >Sure would be nice to put the "net" back in Internet. > >WSimpson(a)UMich.edu > Key fingerprint = 17 40 5E 67 15 6F 31 26 DD 0D B9 9B 6A 15 2C 32 >BSimpson(a)MorningStar.com > Key fingerprint = 2E 07 23 03 C5 62 70 D3 59 B1 4F 5E 1D C2 C1 A2 > -jim

1 0

RE: MCI outages (summary)
by Chris A. Icide 26 Jun '97

26 Jun '97

We've been peering with MCI for a while, and was an MCI customer way back when. It has been my experience that when we make a call to the MCI NOC to report a problem, we have recieved as good (if not better) performance from the NOC as a PEER as we did as a customer. Since I am very happy in the response for all problems that are technical in nature, I would say this is good. However, if the problem in "political" in nature, forget getting any kind of answer from anyone, unless you "know" someone inside. Chris ---------- From: Joe Shaw[SMTP:jshaw@insync.net] Sent: Thursday, June 26, 1997 11:06 AM To: Robert_Gutierrez(a)3com.com Cc: nanog(a)merit.edu Subject: Re: MCI outages (summary) >From what I understand of MCI's peering agreement, you have to come into at least 3 NAPs with DS3 bandwidth or better to even be considered to peer. So, I think if you peer with MCI, you'd definitely carry enough weight with them that they'd take an interest with what problems you have. Joe Shaw - jshaw(a)insync.net NetAdmin - Insync Internet Services "Learn more, and you will never starve." - Paraphrase of Lee On Thu, 26 Jun 1997 Robert_Gutierrez(a)3com.com wrote: > OK, here's a scenario for you. Traceroute fails inside MCI somewhere. So > you > call your upstream, and said upstream only has a peering relationship with > MCI -- ie: not a paying customer. I'm under the impression that unless > you're > a paying customer, then (to quote a 70's phrase) "you don't have nothin' > comin'". > > For those ISP/IBP's out there, can a BGP peer open a trouble ticket with > you to have a problem looked at? Or does the "paying customer" have to > open the TT. What if I can't get the "paying customer" to open up the TT > (ie: you think I can get sex.com to open a TT with their upstream, as if > they > would care longer than the time to hit the "D" key on my message). > > rob > > >

1 0

Re: MCI outages (summary)
by Robert_Gutierrez＠3com.com 26 Jun '97

26 Jun '97

> I think the traceroute fails at this hop. Outages work just like > routing, you pay , X pays MCI, if your not happy you call X, > X calls MCI, if X doesn't call MCI, then why would you buy service from > them? This is the standard operator proceure, if there ever was one. (I hope the formatting is OK. I'm not a Lotus Notes fan ...) OK, here's a scenario for you. Traceroute fails inside MCI somewhere. So you call your upstream, and said upstream only has a peering relationship with MCI -- ie: not a paying customer. I'm under the impression that unless you're a paying customer, then (to quote a 70's phrase) "you don't have nothin' comin'". For those ISP/IBP's out there, can a BGP peer open a trouble ticket with you to have a problem looked at? Or does the "paying customer" have to open the TT. What if I can't get the "paying customer" to open up the TT (ie: you think I can get sex.com to open a TT with their upstream, as if they would care longer than the time to hit the "D" key on my message). rob

4 3

OFF TOPIC: Looking for GNU Make Binary for Solaris x86
by Matthew Pearson 26 Jun '97

26 Jun '97

I am searching for a binary for GNU Make (3.75 perferred) for Solaris 2.5.1 on Intel x86 If anyone has such a beast, please email me and save my sanity (and hours of scouring the web) M

1 0

Lots of non-existant networks
by Eric D. Madison 26 Jun '97

26 Jun '97

There still seems to be a lot of Routes out there that are not in the RADB. I know that ANS is not excepting routes not in a routing database, and others are starting to follow. It's a good idea! I am not getting some of these routes because of the lack of an RADB entry, and it's very frustrating.. Anyone else having the same problems?? Ohh one more thing.. Seems that there are also some routes that are being advertised that don't even have a InterNIC/RIPE/APNIC entry either.. If they don't have an entry, then they are not real "Valid" routes, so I don't want to route them.. but the Origin is from a large provider.. any suggestions? Seems that they have build their whole infrastructure on these routes too. Eric _______________________________________________________ Eric D. Madison - Senior Network Engineer - ACSI - Advanced Data Services - ATM/IP Backbone Group 24 Hour NMC/NOC (800)291-7889 Email: noc(a)acsi.net

6 5

Aol.com missing ??
by Eugene Mondrus 26 Jun '97

26 Jun '97

I am pointing to the UUNET DNS servers, and I am getting "Bad IP Address" for a bunch of domains: aol.com netscape.com erols.com etc .... It is also affecting a few other DNS servers not belonging to UUNET. Any suggestions ??? Gene Mondrus Webmaster Bigfoot.com

3 2

Aol.com missing ??
by Eugene Mondrus 26 Jun '97

26 Jun '97

Whoops, sorry I'm a _Dunce_ . My DNS servers were acting up, and I didn't check it right. Sorry Thanks Gene

1 0

PacBell
by J.D. Falk 26 Jun '97

26 Jun '97

Well, due to the lack of traffic, here's a question that I've been pondering...are there any good reasons (besides MCI's peering requirements) to go into the Pac Bell NAP as well as MAE-West and the PAIX? (This question probably won't have any impact on any decisions; I'm just curious as to people's thoughts on the matter, and it's nice to be able to post something here that isn't about net abuse.) *********************************************************************** J.D. Falk voice: +1-415-482-2840 Supervisor, Network Operations fax: +1-415-482-2844 PRIORI NETWORKS, INC. http://www.priori.net "The People You Know. The People You Trust." ***********************************************************************

7 8

Domain Name Registration Agreement v3.5
by Tom Newell 26 Jun '97

26 Jun '97

6/23/97 Version 3.5 of the Domain Name Registration Agreement has been released. Network Solutions (InterNIC) will accept registrations submitted using either Version 3.0 or Version 3.5 through July 23, 1997. The changes incorporated into Version 3.5 are: 1. Clarification of the terms and conditions of the Domain Name Registration Agreement; 2. Deletion of Section 9 (Invoice Delivery option) from the form since the billing contact is now automatically invoiced by both postal mail and email; 3. Improved instructions. Version 3.5 is available in text format and has also been incorporated into the step-by-step and single page Web-based forms. Associated URL's: ftp://rs.internic.net/templates/domain-template.txt http://rs.internic.net/cgi-bin/itts http://rs.internic.net/cgi-bin/domain Regards, --Tom --------- Tom Newell tomn(a)internic.net Dir, Info Svcs & Tech +1 703 742 4796 Network Solutions, Inc http://www.netsol.com http://rs.internic.net

1 0