September 2000 - Test - lists.nanog.org

RE: UUnet Kansas City/Denver
by Roeland M.J. Meyer 09 Sep '00

09 Sep '00

My upstream is Cerf.NET, whom is apparently now owned by AT&T. They are absorbing the CERF.NET backbone into AT&T. I have been having sporadic connectivity for the past three weeks. Apparently, the feast isn't going quite as smoothly as planned. I expect sporadic major outages for the remainder of the year, from this bunch. > -----Original Message----- > From: Bryan Heitman [mailto:bryanh@communitech.net] > Sent: Saturday, September 09, 2000 5:37 PM > To: nanog(a)merit.edu > Subject: Re: UUnet Kansas City/Denver > > > > Yes Erik we use AT&T, however that is for only local > circuits. We don't > have any long haul with them which is probably why we're not > seeing any > problems... > > If I had to guess I would say that Kingdom City is in AT&Ts path that > connects KC and St. Louis. As it is about in the center of the state > directly east of KC. > > Best, > > > > Bryan Heitman, Vice-President > CommuniTech.Net, Inc. - (800) WEB-HOST > > > ----- Original Message ----- > From: "Adam Korab" <adam(a)inetnebr.com> > To: "Bryan Heitman" <bryanh(a)communitech.net> > Sent: Saturday, September 09, 2000 7:29 PM > Subject: Re: UUnet Kansas City/Denver > > > > On Sat, Sep 09, 2000 at 07:21:15PM -0500, Bryan Heitman wrote: > > > UU is claiming a fiber cut, however we utilize all local > carriers with > > > numerous circuits which are all running fine. > > > > Thank you Bryan. Do you use AT&T? I was thinking that AT&T > > might be the "carrier" UUnet was referring to, and as I > udnerstand, they > > were also having pretty major problems. > > > > --Adam > > -- > > Adam Korab System Administration > > Internet Nebraska (402) 434-8680 x 110 > > > > RFC 882 put the dot in .com, not Sun Microsystems > >

1 0

Re: UUnet Kansas City/Denver
by Bryan Heitman 09 Sep '00

09 Sep '00

Yes Erik we use AT&T, however that is for only local circuits. We don't have any long haul with them which is probably why we're not seeing any problems... If I had to guess I would say that Kingdom City is in AT&Ts path that connects KC and St. Louis. As it is about in the center of the state directly east of KC. Best, Bryan Heitman, Vice-President CommuniTech.Net, Inc. - (800) WEB-HOST ----- Original Message ----- From: "Adam Korab" <adam(a)inetnebr.com> To: "Bryan Heitman" <bryanh(a)communitech.net> Sent: Saturday, September 09, 2000 7:29 PM Subject: Re: UUnet Kansas City/Denver > On Sat, Sep 09, 2000 at 07:21:15PM -0500, Bryan Heitman wrote: > > UU is claiming a fiber cut, however we utilize all local carriers with > > numerous circuits which are all running fine. > > Thank you Bryan. Do you use AT&T? I was thinking that AT&T > might be the "carrier" UUnet was referring to, and as I udnerstand, they > were also having pretty major problems. > > --Adam > -- > Adam Korab System Administration > Internet Nebraska (402) 434-8680 x 110 > > RFC 882 put the dot in .com, not Sun Microsystems

1 0

UUnet Kansas City/Denver
by Adam Korab 09 Sep '00

09 Sep '00

My T1s to UUnet's Kansas City POP began having routing trouble this afternoon about 3:00pm central time. The lines are up, but no data is passing through them. A sh ip bgp sum reports that only 563 prefixes are coming through, as opposed to the normal 70k-80k. www.noc.uu.net is terribly vague about the trouble, and I can't get through to anyone on their tech support line; does anyone have a ticket number, ETR, or other information about this problem? Thanks. --Adam -- Adam Korab System Administration Internet Nebraska (402) 434-8680 x 110 RFC 882 put the dot in .com, not Sun Microsystems

2 1

Concentric Problems?
by Robert L. Harris 09 Sep '00

09 Sep '00

I'm having some very weird problems with my iDSL. The DSLAM says there's nothing wrong with the line, there are no errors on either end, but I ping timeout and can't even traceroute through it when it goes down. Concentric says there's nothing wrong even though they did finally see the problem the other day. Their solution was to replace my iDSL router and close the ticket and the problem isn't gone. 2 Questions: 1) Anyone know any useful phone #'s at concentric? The help desk insists that the ONLY way to call anyone there is to go through the 800 number, which has a 30-90 wait and not even managers have a direct extension. Everyone stands by this BS. 2) Anyone have any suggestions on things to look at? My Robert :wq! --------------------------------------------------------------------------- Robert L. Harris | Micros~1 : Senior System Engineer | For when quality, reliability at RnD Consulting | and security just aren't \_ that important! DISCLAIMER: These are MY OPINIONS ALONE. I speak for no-one else. FYI: perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'

1 0

Re: Worldcom fiber outage
by Sean Donelan 08 Sep '00

08 Sep '00

MFS circuits have been coming back online in the last hour (about 6pm PDT) in the San Francisco bay area. Nasa Ames seems to be back in service for most peering. The location of the cut was identified as 30 miles south of San Francisco. I'm not sure who swapped fiber with whom, and who is sharing right of ways with others. I've heard both Qwest and MFS/Worldcom as the actual owner of the fiber right of way in question. I don't know the legal owner of the fiber, or if it really matters whether its the carrier's own fiber or their circuits are running in someone else's innerduct when the circuit goes down. Interactive week covers some of the reason why this cut may have affected things more than normal. The bay bridge fiber had a scheduled maintenance window, and was out of service, when the cut occured. http://www.zdnet.com/intweek/stories/news/0,4164,2626180,00.html Circuit grooming occurs more than carriers admit. When was the last time you checked your DLR? Although there is no evidence cuts happen more often when your redundent link is out of service, they're the ones everyone remembers.

1 0

Re: Wisconsin fiber cut
by Keith Woodworth 08 Sep '00

08 Sep '00

On Fri, 8 Sep 2000, missnglnk wrote: >>On Fri, 8 Sep 2000, Keith Woodworth wrote: >> >>> Is this what you do all day Sean? Track fiber cuts over N.A.? >>> :) >> >>When you work for a major backbone, you should know what's down and >>affecting your network instead of answering questions with "I dunno >>what's wrong in Wisconsin." Acutally I forgot to add that yes you are right. I had a few customers call and say that certain sites were awful slow today and I was able to at least relate to them that certain network outages might be the cause.

1 0

Re: Wisconsin fiber cut
by Keith Woodworth 08 Sep '00

08 Sep '00

On Fri, 8 Sep 2000, missnglnk wrote: >>When you work for a major backbone, you should know what's down and >>affecting your network instead of answering questions with "I dunno >>what's wrong in Wisconsin." >> >>Replace "Wisconsin" with any other city that has any bandwidth. Which pretty much defines any city or town in most of North America. On another note is anyone here based in the lower part of Alaska? (Ketchican, etc) Keith

1 0

Wisconsin fiber cut
by Sean Donelan 08 Sep '00

08 Sep '00

Southwestern bell has reported a fiber cut in Wisconsin. It isolated six 9-1-1 answering points around Watertown. A contractor is being blamed for the fiber cut. There are no reports yet on the FCC website about any problems in the San Francisco bay area.

2 1

Fiber woes
by Jason DeCamp 08 Sep '00

08 Sep '00

i may have already missed this, but what was cut on the west coast, and how? anyone know? Thanx -Jay

1 0

Root zone change --- Informational Message
by Verd, Brad 08 Sep '00

08 Sep '00

Informational Message: The IP for k.gtld-servers.net will be changed in the authoritative list for .com, .net, and .org. Changes will be reflected in the zone with serial number 2000090801 The old IP for k.gtld-servers.net is 195.8.99.11 and the new IP is 213.177.194.5 The old server will remain in service for a minimum of a week. -------------------------------------- Brad Verd gTLD Operations Manager Network Solutions Registry Email - bverd(a)netsol.com ---------------------------------------

1 0