From owner-freebsd-questions Fri Sep 27 13:28:43 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA03973 for questions-outgoing; Fri, 27 Sep 1996 13:28:43 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA03934 for ; Fri, 27 Sep 1996 13:28:39 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id NAA02823; Fri, 27 Sep 1996 13:29:53 -0700 (PDT) Message-Id: <199609272029.NAA02823@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Ben Black cc: eischen@vigrid.com (Daniel Eischen), questions@freebsd.org Subject: Re: CRL In-reply-to: Your message of "Fri, 27 Sep 1996 10:43:46 CDT." <9609271544.AA05476@squid.gage.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 27 Sep 1996 13:29:53 -0700 Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >i must apologize for assuming that sprint was being straight about CRL and >peering problems. i'll be going to UUNet for my second connection. Here is the response to all of this from the horse's mouth (Jim Couch is the owner and CEO of CRL Network Services): --- >From: Jim Couch >Message-Id: <199609271537.AA28466@crl.crl.com> >To: dg@root.com >Subject: Re: route flapping? David, I should have some good news for you shortly regarding the extra DS3 that we are adding in Chicago. There is no flap to MCI that I am aware of. Here is the first few lines of the bgp summary from the actual router. MCI is AS 3561 and was last reset 1 week and 4 days ago. gwmaew>show ip bgp sum Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State 149.20.64.7 4 1280 5640463 94371 68727374 0 0 1w2d 165.113.25.1 4 2041 5650768 1748961 68737617 0 0 3d15 165.113.55.1 4 2041 8451692 1658358 68737617 2 0 6d16 192.203.230.25 4 668 69047 58750 68727374 0 0 4d01 198.32.136.5 4 1740 34603 42899 0 0 0 5w3d Active > 198.32.136.12 4 3561 750994 110712 68727374 0 0 1w4d 198.32.136.13 4 5646 288790 110988 68729941 0 0 2w0d I appreciate your patience in dealing with the "your 7500 is a poor router which isnt approved" line of reasoning that surfaces from time to time when sprint connected networks cant get through. The dampening that sprint has been doing has taken whole sets of customers offline for as little as one bgp transition. They have set the dampening on the cix router peer such that if the connection goes down they will ignore the routes when it comes back up for a couple hours. The problem used to be in the cix router being out of computrons, but that iss no longer the case. The sl-stk5 (or 6?) router is the one that is now out of CPU and it is shutting off customers when it drops bgp due to high CPU load. We have been getting calls from sprint customers who were un-routed for a few hours and were told by sprint that sprint will dampen anywhere there is a problem, presumably on their distribution routers as well. I dont understand why they keep adding parts to their network. It seems clear that they should build a "sprint2" and treat it as a second outside network. Perhaps the cisco BFR "big fast router" will materialize soon and save their day. We have just added a Vienna VA office to upgrade our MAE-E connection to 100 MBPS sonet FDDI with the addition of a second 7500 router out there. We are moving out of the Colo with Cable and Wireless and just down the street from the MAE-E building. We will be on-net with an OC-12 there in the next 2 weeks. Chicago is not far behind; I'll drop you some email when I get the exact date. Regards, -Jim --- -DG David Greenman Core-team/Principal Architect, The FreeBSD Project