After re-reading the following message I wanted to make sure I was clear that I am *not* currently having any connectivity problems with uu.net. It just happens often enough (and since it was brought up) that I wanted to find out what other people did to resolve this.
I have recieved a couple of nice notes from people at uu.net offering to help in the future. I will be keeping those on file for future reference. I would like to say that my comments below still stand. I wouldn't have needed to contact the uunet NOC if a public looking glass was provided. On Fri, 29 Mar 2002, Forrest W. Christian wrote: > Date: Fri, 29 Mar 2002 12:10:18 +0000 (GMT) > From: Forrest W. Christian <[EMAIL PROTECTED]> > To: batz <[EMAIL PROTECTED]> > Cc: Stephen J. Wilcox <[EMAIL PROTECTED]>, > Mark E. Mallett <[EMAIL PROTECTED]>, [EMAIL PROTECTED] > Subject: Re: Help with bad announcement from UUnet > > > I've obviously caused a stir. > > Before I proceed, let me say I'm going to continue mentioning UU.net as > I've had experience there... The responses to this list indicate this is > a more widespread problem, so please don't take this as necessarily > badmouthing uu.net. > > Let me first say EXACTLY what I was looking for. I'm multihomed. All > I've wanted out of uu.net each time I've called is a traceroute and/or BGP > output to determine which path my packets were heading back towards me on > so *I* could get the problem fixed. I.E. to determine where the loss was > really occuring and/or who was mis-announcing a prefix. > > In every case where I've tried to contact uu.net it's been obvious that as > soon as traffic reaches their AS, everything goes to pot. Without being > able to take a peek inside their network (via a traceroute or sh ip bgp) > It's almost impossible to tell where the problem lies, since the problem > is obviously with traffic getting back to my network. I agree with batz: > > On Fri, 29 Mar 2002, batz wrote: > > Because their network transits _most_ internet traffic and > > as a courtesy, they should provide some bare level of > > diagnostic services to the rest of the network. > > I can't think of a case where I've called the uu.net noc where I wanted > more information than could have been queried through a standard looking > glass (I.E. traceroute and BGP information). In fact, if uu.net provided > a looking glass we probably wouldn't be having this discussion. > > Without rambling much further I'll add this: Yes, I realize there are > scaling issues. Yes, I do want to call my upstream to get it fixed. No, > I don't expect uu.net to own the problem (unless of course it IS their > problem). BUT I can't tell which of my upstreams is having the problem in > order to call them without a BGP or traceroute from the provider we're > having problems reaching. > > - Forrest W. Christian ([EMAIL PROTECTED]) AC7DE > ---------------------------------------------------------------------- > The Innovation Machine Ltd. P.O. Box 5749 > http://www.imach.com/ Helena, MT 59604 > Home of PacketFlux Technogies and BackupDNS.com (406)-442-6648 > ---------------------------------------------------------------------- > Protect your personal freedoms - visit http://www.lp.org/ > - Forrest W. Christian ([EMAIL PROTECTED]) AC7DE ---------------------------------------------------------------------- The Innovation Machine Ltd. P.O. Box 5749 http://www.imach.com/ Helena, MT 59604 Home of PacketFlux Technogies and BackupDNS.com (406)-442-6648 ---------------------------------------------------------------------- Protect your personal freedoms - visit http://www.lp.org/