North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: moscow

  • From: John Fraizer
  • Date: Thu Dec 07 03:25:28 2000 
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