Date: Fri, 27 Sep 1996 01:22:42 -0700 From: David Greenman <dg@root.com> To: eischen@vigrid.com (Daniel Eischen) Cc: freebsd-questions@FreeBSD.org Subject: Re: Sprints response to to wcarchive connectivity problems Message-ID: <199609270822.BAA01847@root.com> In-Reply-To: Your message of "Thu, 26 Sep 1996 14:21:48 EDT." <9609261821.AB24484@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>I've been having problems with connectivity to wcarchive. It's happened >quite a few times in the past, and I've noted all the responses saying >it's Sprints problem. I finally got tired of dealing with thesse >transient problems, so I started complaining to my ISP and his Sprint >representative. > >Here is Sprints response (in my ISPs words). While this may be the cause >of recent problems (last week or so), is it representative of most of >the other Sprint connectivity problems? > > "cdrom.com's provider, crl.com, is connected to the internet via a > non-approved poor router. The router is hosing causing flapping problems. > This is also due to the fact that crl does not properly peer. In other > words, crl and therefore crl's customer is not holding up to acceptable use > policies. The destination is deliberately blocked when the router flaps so > as to prevent flapping throughout the network." The person who said this at Sprint doesn't have a grasp of the problem. The problem has nothing to do with CRL. It has to do with Sprint's BGP session going down at the CIX (Commercial Internet Exchange). I can only hazard a guess as to why, but one possibility is that Sprint's T1 (yes, *T1*) to the CIX is overloaded. The problem used to be caused by the CIX router being overloaded. This has recently been fixed (a new 7513 was purchased and many of the connections were offloaded to it). Sprint is still connected to the old 7000. In any case, the CIX has absolutely zilch to do with CRL. That person at Sprint also fails to understand that CRL has dozens of high end Cisco routers (not to mention at least 30 Cascade ATM switches) and connects to most of the primary NAPs via DS3 circuits. Sprint refuses to peer with them because CRL doesn't connect to the Chicago NAP (and thus CRL doesn't meet Sprint's '3 primary NAPs, seperated by 1000 miles' requirement). In other words, what Sprint told your ISP was a complete lie. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609270822.BAA01847>