I know this is NAnog, but who else can I ask about msu1-gw.Moscow.ST.NET (194.186.0.250) which seems to be looping. Chris
Do you have any specifics? Perhaps a traceroute showing the loops? Possibly a "sh ip bgp" of the (an) effected network? --- John Fraizer EnterZone, Inc On Thu, 7 Dec 2000, Chris Beggy wrote:
I know this is NAnog, but who else can I ask about
msu1-gw.Moscow.ST.NET (194.186.0.250)
which seems to be looping.
Chris
From: John Fraizer <nanog@EnterZone.Net> Subject: Re: moscow Date: Thu, 7 Dec 2000 01:43:14 -0500 (EST)
Do you have any specifics? Perhaps a traceroute showing the loops? Possibly a "sh ip bgp" of the (an) effected network?
---
Thanks for asking! Here's a traceroute: 1 conodoguinet.kippona.com (207.106.63.35) 1.335 ms 0.938 ms 2.845 ms 2 hosted-by.kippona.com (207.106.63.41) 3.025 ms 2.903 ms 2.984 ms 3 1.145.8.207.in-addr.arpa (207.8.145.1) 8.027 ms 7.249 ms 7.399 ms 4 consh-colo-gsr.netaxs.com (207.106.32.13) 8.699 ms 6.863 ms 6.965 ms 5 conshie-sdfc-l.netaxs.com (207.106.0.9) 7.58 ms 7.171 ms 7.335 ms 6 sdfc-l3-l.netaxs.net (207.106.3.245) 7.932 ms 7.323 ms 7.303 ms 7 l3-psk-t3-r.netaxs.net (207.106.3.202) 8.24 ms 8.647 ms 8.537 ms 8 192.157.69.10 (192.157.69.10) 11.686 ms 10.503 ms 10.558 ms 9 sl-bb22-pen-3-2.sprintlink.net (144.232.5.65) 10.084 ms 11.05 ms 10.02 ms 10 sl-bb22-nyc-13-0.sprintlink.net (144.232.9.69) 10.562 ms 11.376 ms 9.977 ms 11 sl-bb10-nyc-10-0.sprintlink.net (144.232.13.158) 11.204 ms 10.465 ms 10.297 ms 12 sl-gtscarrier-1-0-0.sprintlink.net (160.81.101.2) 14.465 ms 14.046 ms 14.147 ms 13 gblon505-tc-p6-1.ebone.net (195.158.229.42) 80.912 ms 81.177 ms 80.774 ms 14 bebru204-tc-p5-0.ebone.net (195.158.232.42) 86.61 ms 85.78 ms 86.7 ms 15 bebru203-tc-p2-0.ebone.net (195.158.225.81) 86.862 ms 85.326 ms 85.813 ms 16 nlams303-tc-p1-0.ebone.net (195.158.225.86) 89.264 ms 88.304 ms 90.107 ms 17 dedus205-tc-p8-0.ebone.net (213.174.70.133) 92.158 ms 92.392 ms 91.169 ms 18 dkcop204-tb-p3-0.ebone.net (213.174.71.50) 118.498 ms 117.283 ms 117.138 ms 19 dkcop205-tb-p2-0.ebone.net (195.158.226.118) 118.582 ms 118.688 ms 117.751 ms 20 sesto302-tc-p5-0.ebone.net (213.174.71.101) 110.066 ms 110.533 ms 111.304 ms 21 sesto502-tb-r5-0.ebone.net (213.174.69.148) 112.819 ms 112.002 ms 110.133 ms 22 195.158.226.54 (195.158.226.54) 110.379 ms 110.625 ms 111.283 ms 23 cisco0.Moscow.ST.NET (194.186.157.161) 153.728 ms cisco0.Moscow.ST.NET (194.186.157.217) 135.423 ms 139.552 ms 24 cisco02.Moscow.ST.NET (194.186.157.182) 139.811 ms 137.807 ms 133.11 ms 25 cisco13.Moscow.ST.NET (194.186.157.242) 137.544 ms cisco13.Moscow.ST.NET (194.186.157.177) 136.035 ms 133.5 ms 26 cisco12.Moscow.ST.NET (194.186.157.237) 139.164 ms 139.081 ms 145.021 ms 27 msu1-gw.Moscow.ST.NET (194.186.0.250) 163.198 ms 146.187 ms 157.823 ms 28 msu1-gw.Moscow.ST.NET (194.186.0.250) 161.157 ms * * 29 msu1-gw.Moscow.ST.NET (194.186.0.250) 150.03 ms * * 30 * msu1-gw.Moscow.ST.NET (194.186.0.250) 141.99 ms * Chris
Looks like one of two things is happening: 1) msu1-gw.Moscow.ST.NET (194.186.0.250) is announcing a more specific route to your target that it doesn't have. 2) Your target lives directly behind msu1-gw.Moscow.ST.NET (194.186.0.250 and is dead. Without knowing the target IP address, it's hard to tell. --- John Fraizer EnterZone, Inc On Thu, 7 Dec 2000, Chris Beggy wrote:
From: John Fraizer <nanog@EnterZone.Net> Subject: Re: moscow Date: Thu, 7 Dec 2000 01:43:14 -0500 (EST)
Do you have any specifics? Perhaps a traceroute showing the loops? Possibly a "sh ip bgp" of the (an) effected network?
---
Thanks for asking!
Here's a traceroute: 1 conodoguinet.kippona.com (207.106.63.35) 1.335 ms 0.938 ms 2.845 ms 2 hosted-by.kippona.com (207.106.63.41) 3.025 ms 2.903 ms 2.984 ms 3 1.145.8.207.in-addr.arpa (207.8.145.1) 8.027 ms 7.249 ms 7.399 ms 4 consh-colo-gsr.netaxs.com (207.106.32.13) 8.699 ms 6.863 ms 6.965 ms 5 conshie-sdfc-l.netaxs.com (207.106.0.9) 7.58 ms 7.171 ms 7.335 ms 6 sdfc-l3-l.netaxs.net (207.106.3.245) 7.932 ms 7.323 ms 7.303 ms 7 l3-psk-t3-r.netaxs.net (207.106.3.202) 8.24 ms 8.647 ms 8.537 ms 8 192.157.69.10 (192.157.69.10) 11.686 ms 10.503 ms 10.558 ms 9 sl-bb22-pen-3-2.sprintlink.net (144.232.5.65) 10.084 ms 11.05 ms 10.02 ms 10 sl-bb22-nyc-13-0.sprintlink.net (144.232.9.69) 10.562 ms 11.376 ms 9.977 ms 11 sl-bb10-nyc-10-0.sprintlink.net (144.232.13.158) 11.204 ms 10.465 ms 10.297 ms 12 sl-gtscarrier-1-0-0.sprintlink.net (160.81.101.2) 14.465 ms 14.046 ms 14.147 ms 13 gblon505-tc-p6-1.ebone.net (195.158.229.42) 80.912 ms 81.177 ms 80.774 ms 14 bebru204-tc-p5-0.ebone.net (195.158.232.42) 86.61 ms 85.78 ms 86.7 ms 15 bebru203-tc-p2-0.ebone.net (195.158.225.81) 86.862 ms 85.326 ms 85.813 ms 16 nlams303-tc-p1-0.ebone.net (195.158.225.86) 89.264 ms 88.304 ms 90.107 ms 17 dedus205-tc-p8-0.ebone.net (213.174.70.133) 92.158 ms 92.392 ms 91.169 ms 18 dkcop204-tb-p3-0.ebone.net (213.174.71.50) 118.498 ms 117.283 ms 117.138 ms 19 dkcop205-tb-p2-0.ebone.net (195.158.226.118) 118.582 ms 118.688 ms 117.751 ms 20 sesto302-tc-p5-0.ebone.net (213.174.71.101) 110.066 ms 110.533 ms 111.304 ms 21 sesto502-tb-r5-0.ebone.net (213.174.69.148) 112.819 ms 112.002 ms 110.133 ms 22 195.158.226.54 (195.158.226.54) 110.379 ms 110.625 ms 111.283 ms 23 cisco0.Moscow.ST.NET (194.186.157.161) 153.728 ms cisco0.Moscow.ST.NET (194.186.157.217) 135.423 ms 139.552 ms 24 cisco02.Moscow.ST.NET (194.186.157.182) 139.811 ms 137.807 ms 133.11 ms 25 cisco13.Moscow.ST.NET (194.186.157.242) 137.544 ms cisco13.Moscow.ST.NET (194.186.157.177) 136.035 ms 133.5 ms 26 cisco12.Moscow.ST.NET (194.186.157.237) 139.164 ms 139.081 ms 145.021 ms 27 msu1-gw.Moscow.ST.NET (194.186.0.250) 163.198 ms 146.187 ms 157.823 ms 28 msu1-gw.Moscow.ST.NET (194.186.0.250) 161.157 ms * * 29 msu1-gw.Moscow.ST.NET (194.186.0.250) 150.03 ms * * 30 * msu1-gw.Moscow.ST.NET (194.186.0.250) 141.99 ms *
Chris
Looks like one of two things is happening:
1) msu1-gw.Moscow.ST.NET (194.186.0.250) is announcing a more specific route to your target that it doesn't have. 2) Your target lives directly behind msu1-gw.Moscow.ST.NET (194.186.0.250 and is dead.
Without knowing the target IP address, it's hard to tell.
Thanks. The target is 212.16.7.66. Chris
On Thu, 7 Dec 2000, Chris Beggy wrote:
Looks like one of two things is happening:
1) msu1-gw.Moscow.ST.NET (194.186.0.250) is announcing a more specific route to your target that it doesn't have. 2) Your target lives directly behind msu1-gw.Moscow.ST.NET (194.186.0.250 and is dead.
Without knowing the target IP address, it's hard to tell.
Thanks. The target is 212.16.7.66.
Chris
Our view of it: BGP routing table entry for 212.16.0.0/19 Paths: (2 available, best #1, table Default-IP-Routing-Table) 6347 701 1755 3216 8592, (aggregated by 8592 212.16.0.97) 64.241.88.65 from 64.241.88.65 (1.0.0.102) Origin IGP, metric 1000, localpref 100, valid, external, atomic-aggregate, best Community: 6347:1102 6347:5000 6347:5001 13944:6347 Last update: Wed Dec 6 20:39:44 2000 6259 3549 1239 1755 3216 8592, (aggregated by 8592 212.16.0.97) 209.115.127.21 from 209.115.127.21 (206.183.226.33) Origin IGP, metric 1010, localpref 100, valid, external, atomic-aggregate Community: 13944:6259 Last update: Wed Dec 6 06:58:11 2000 <snip> 20 195.158.226.54 (195.158.226.54) 157.093 ms 156.952 ms 187.512 ms 21 cisco0.Moscow.ST.NET (194.186.157.161) 179.581 ms 181.016 ms 178.780 ms 22 cisco02.Moscow.ST.NET (194.186.157.170) 183.773 ms 184.158 ms 180.691 ms 23 cisco13.Moscow.ST.NET (194.186.157.177) 182.534 ms cisco13.Moscow.ST.NET (194.186.157.242) 202.605 ms 197.822 ms 24 cisco12.Moscow.ST.NET (194.186.157.237) 189.250 ms 183.095 ms 192.375 ms 25 msu1-gw.Moscow.ST.NET (194.186.0.250) 237.427 ms 199.915 ms 182.212 ms 26 msu1-gw.Moscow.ST.NET (194.186.0.250) 184.444 ms !X * * --- John Fraizer EnterZone, Inc
On Thu, Dec 07, 2000 at 01:55:19AM -0500, Chris Beggy wrote: Chris- What are you tracerouting?
Here's a traceroute: 1 conodoguinet.kippona.com (207.106.63.35) 1.335 ms 0.938 ms 2.845 ms 2 hosted-by.kippona.com (207.106.63.41) 3.025 ms 2.903 ms 2.984 ms 3 1.145.8.207.in-addr.arpa (207.8.145.1) 8.027 ms 7.249 ms 7.399 ms 4 consh-colo-gsr.netaxs.com (207.106.32.13) 8.699 ms 6.863 ms 6.965 ms 5 conshie-sdfc-l.netaxs.com (207.106.0.9) 7.58 ms 7.171 ms 7.335 ms 6 sdfc-l3-l.netaxs.net (207.106.3.245) 7.932 ms 7.323 ms 7.303 ms 7 l3-psk-t3-r.netaxs.net (207.106.3.202) 8.24 ms 8.647 ms 8.537 ms 8 192.157.69.10 (192.157.69.10) 11.686 ms 10.503 ms 10.558 ms
-Basil
participants (3)
-
Basil Kruglov -
Chris Beggy -
John Fraizer