Routing problems at sprintnap?

Hi, I'm seeing some weird routes while going through sprint-nap. Is DISA.MIL announcing some invalid routes? traceroute www.sprintlink.net traceroute to sprintlink.sprintbiz.com (198.70.62.124), 30 hops max, 40 byte packets 1 Hoofddorp3.cistron.net (195.64.68.3) 2.892 ms 3.442 ms 3.078 ms 2 go1-ams-s1.global-one.nl (194.235.74.241) 17.61 ms 6.46 ms 16.193 ms 3 car1-ams-fe0/1.global-one.nl (194.235.110.33) 3.631 ms 3.284 ms * 4 bar.global-one.nl (194.235.110.1) 4.546 ms 3.714 ms 3.666 ms 5 gsl-penn-2-Serial8/4.gsl.net (204.59.137.69) 131.344 ms 149.25 ms 118.781 ms 6 sprint-nap.disa.mil (192.157.69.45) 102.682 ms 112.918 ms 104.687 ms 7 * * * 8 * * * 9 131.57.128.1 (131.57.128.1) 507.96 ms 382.096 ms * 10 TYNDALL-AFIN-Serial2/0.AFIN.AF.MIL (143.230.221.26) 687.843 ms 405.198 ms 417.191 ms traceroute ns2.iac.net traceroute to ns2.iac.net (198.180.60.134), 30 hops max, 40 byte packets 1 Hoofddorp3.cistron.net (195.64.68.3) 88.961 ms 8.377 ms 3.277 ms 2 go1-ams-s1.global-one.nl (194.235.74.241) 5.149 ms 5.124 ms 19.537 ms 3 car1-ams-fe0/1.global-one.nl (194.235.110.33) 7.363 ms 15.485 ms 9.399 ms 4 bar.global-one.nl (194.235.110.1) 11.487 ms 6.15 ms 7.142 ms 5 gsl-penn-2-Serial8/4.gsl.net (204.59.137.69) 91.055 ms 93.618 ms 114.098 ms 6 sprint-nap.disa.mil (192.157.69.45) 116.977 ms 118.616 ms 122.311 ms 7 1-sprint-nap.internetmci.net (192.157.69.11) 324.678 ms 141.545 ms 232.146 ms Thanks, -Ed -- Edvard Tuinder Cistron Internet Services Finger ed@cistron.nl for PGP key ``I must fear Evil, for I am but mortal and mortals can only die''

Here you go Ed, June 13, 1997 11:00 EDT. We are experiencing routing instabilities due to bad BGP announcements coming from one of the international network service providers that we peer with in Pennsauken, NJ. These announcements will cause delay and/or unreachable states across the country as the network reconverges around the problem. We have isolated the problem, and are working to clear the bad routes from our network. We apologize for the routing instabilities that you may be experiencing, and appreciate your patience on this issue as we work to resolve it. Thank You Rob Rockell Sprintlink ISC. ->Hi, -> ->I'm seeing some weird routes while going through sprint-nap. Is DISA.MIL ->announcing some invalid routes? -> -> traceroute www.sprintlink.net ->traceroute to sprintlink.sprintbiz.com (198.70.62.124), 30 hops max, 40 byte packets -> 1 Hoofddorp3.cistron.net (195.64.68.3) 2.892 ms 3.442 ms 3.078 ms -> 2 go1-ams-s1.global-one.nl (194.235.74.241) 17.61 ms 6.46 ms 16.193 ms -> 3 car1-ams-fe0/1.global-one.nl (194.235.110.33) 3.631 ms 3.284 ms * -> 4 bar.global-one.nl (194.235.110.1) 4.546 ms 3.714 ms 3.666 ms -> 5 gsl-penn-2-Serial8/4.gsl.net (204.59.137.69) 131.344 ms 149.25 ms 118.781 ms -> 6 sprint-nap.disa.mil (192.157.69.45) 102.682 ms 112.918 ms 104.687 ms -> 7 * * * -> 8 * * * -> 9 131.57.128.1 (131.57.128.1) 507.96 ms 382.096 ms * ->10 TYNDALL-AFIN-Serial2/0.AFIN.AF.MIL (143.230.221.26) 687.843 ms 405.198 ms 417.191 ms -> -> -> traceroute ns2.iac.net ->traceroute to ns2.iac.net (198.180.60.134), 30 hops max, 40 byte packets -> 1 Hoofddorp3.cistron.net (195.64.68.3) 88.961 ms 8.377 ms 3.277 ms -> 2 go1-ams-s1.global-one.nl (194.235.74.241) 5.149 ms 5.124 ms 19.537 ms -> 3 car1-ams-fe0/1.global-one.nl (194.235.110.33) 7.363 ms 15.485 ms 9.399 ms -> 4 bar.global-one.nl (194.235.110.1) 11.487 ms 6.15 ms 7.142 ms -> 5 gsl-penn-2-Serial8/4.gsl.net (204.59.137.69) 91.055 ms 93.618 ms 114.098 ms -> 6 sprint-nap.disa.mil (192.157.69.45) 116.977 ms 118.616 ms 122.311 ms -> 7 1-sprint-nap.internetmci.net (192.157.69.11) 324.678 ms 141.545 ms 232.146 ms -> -> ->Thanks, -> ->-Ed ->-- ->Edvard Tuinder ->Cistron Internet Services Finger ed@cistron.nl for PGP key -> ``I must fear Evil, for I am but mortal and mortals can only die'' -> --- Jeff Farrelly jeff@good.net (602)303.9500 ext.3271

On Sat, 14 Jun 1997, Edvard Tuinder wrote:
Hi,
I'm seeing some weird routes while going through sprint-nap. Is DISA.MIL announcing some invalid routes?
Hello, this is what I just received... -tom
From postout@sprint.net Sat Jun 14 00:25:56 1997 Date: Fri, 13 Jun 1997 12:09:05 -0400 (EDT) From: Outage Poster <postout@sprint.net> Reply-To: owner-outage@dal.net To: outage@sprint.net Subject: OUTAGE: pennsauken BGP
June 13, 1997 11:00 EDT. We are experiencing routing instabilities due to bad BGP announcements coming from one of the international network service providers that we peer with in Pennsauken, NJ. These announcements will cause delay and/or unreachable states across the country as the network reconverges around the problem. We have isolated the problem, and are working to clear the bad routes from our network. We apologize for the routing instabilities that you may be experiencing, and appreciate your patience on this issue as we work to resolve it. Thank You Rob Rockell Sprintlink ISC. ---------------------------------------------------------------------------- This collection of lists is provided as a DALnet service - http://www.dal.net/ To unsubscribe, e-mail majordomo@dal.net with a body of 'unsubscribe outage'

AS 400 started announcing some 8000+ routes some time between 17:00 and 18:00 EDT today. AS 400 is behind AS 568 (DISA). Various folks have now blocked either just _400_ from DISA or blocked all routes with DISA or turned off peering with DISA. Most of these bad routes are now gone in most places. There are still lingering pockets of bad routes due to folks running old cisco code - remember the AS 7700 incident where the bad routes hung around for at least 24+ hours? Cisco has fixed this stuck route problem, but not everyone has upgraded all of their routers. A work around is to clear BGP sessions to get rid of the routes. [I've been on the phone with various NOCs and engineers with Sprint, MCI, Verio (my NOC) and DISA for the last several hours.] --asp@partan.com (Andrew Partan)

There are still lingering pockets of bad routes due to folks running old cisco code - remember the AS 7700 incident where the bad routes hung around for at least 24+ hours? Cisco has fixed this stuck route problem, but not everyone has upgraded all of their routers. A work around is to clear BGP sessions to get rid of the routes.
Oops - s/7700/7007/. Sorry about that. Humm: I wonder how many ISPs still have blocks in place for _7007_? --asp@partan.com (Andrew Partan)
participants (4)
-
Andrew Partan
-
Edvard Tuinder
-
Jeff Farrelly
-
Thomas Trede