nanog mailing list archives

Re: Need help from UUNet's routing specialist!


From: Erik-Jan Bos <erik-jan.bos () surfnet nl>
Date: Thu, 09 Dec 1999 18:11:00 +0100


Dmitry,

We (as8470) are Teleglobe customer. And we experience terrible
delays on Teleglobe to UUNet interconnect points. Teleglobe's customer
support engineers insist, that the problem caused by UUNet's routes
prioritization.
But I belive that this assymetric routing initiated by Teleglobe, not
UUNet. 

We are a TGO customer as well and we do not see the problem. Here's a
traceroute:

surgeon bos % date
Thu Dec  9 18:10:43 CET 1999

surgeon bos % traceroute www.uu.net
traceroute to www.uu.net (208.243.117.123): 1-30 hops, 38 byte packets
 1  surroute.surfnet.nl (192.87.109.1)  0.554 ms  0.441 ms  0.399 ms
 2  AR1.Utrecht.surf.net (145.41.49.161)  101 ms  2.28 ms  1.82 ms
 3  AR2.Utrecht.surf.net (145.41.7.181)  1.48 ms  2.14 ms  1.51 ms
 4  BR7.Amsterdam.surf.net (145.41.7.125)  2.87 ms  2.70 ms  2.49 ms
 5  BR2.Amsterdam.surf.net (145.41.7.146)  2.91 ms  2.71 ms  2.75 ms
 6  BR2.NewYork.surf.net (145.41.7.110)  79.5 ms  79.9 ms  80.0 ms
 7  if-6-3.core1.NewYork.Teleglobe.net (207.45.196.129)  79.8 ms  79.8 ms 79.7 ms
 8  if-0-3.core2.nqt.Teleglobe.net (207.45.223.178)  80.0 ms  80.1 ms 80.6 ms
 9  if-1-0.core1.Washington.Teleglobe.net (207.45.223.170)  84.6 ms  84.7 ms  84.8 ms
10  if-10-0-0.bb1.Washington.Teleglobe.net (207.45.221.195)  85.3 ms 85.6 ms  84.8 ms
11  Serial3-1-1.GW1.DCA3.ALTER.NET (157.130.39.89)  86.7 ms  87.2 ms 87.0 ms
12  110.ATM3-0.XR1.DCA1.ALTER.NET (146.188.161.54)  86.3 ms  86.0 ms  85.7 ms 
13  195.ATM8-0-0.GW1.DCA1.ALTER.NET (146.188.161.17)  87.2 ms  88.0 ms 86.6 ms
14  260.GW1.TCO3.customer.ALTER.NET (157.130.33.222)  220 ms  112 ms  136 ms
15  prod-334a.tco3.web.uu.net (208.243.113.236)  92.7 ms  *  88.3 ms

Perhaps this is fixed?

Could you please send me 'sh ip bgp 195.128.65.33' performed at
Serial3-1-1.GW1.DCA3.ALTER.NET (157.130.39.89). 

I am expecting to see communities or MEDs set at TG router that lowres
route priority and makes traffic to go back via _Seattle_Denver_Chicago_NY_.
Any help is _greatly_ appreciated!

---------------------
Example of delays:
---------------------
nyy-1#trace        
Protocol [ip]:      
Target IP address: www.uu.net   
Translating "www.uu.net"...domain server (195.128.64.3) [OK]

Source address: 195.128.65.33 
Loose, Strict, Record, Timestamp, Verbose[none]: 
Type escape sequence to abort.
Tracing the route to www.uu.net (208.243.117.123)

1 if-0-1-0.bb6.NewYork.Teleglobe.net (207.45.205.13) [AS 6453] 0 msec 0 msec
 0 msec
2 if-3-0.core2.nqt.Teleglobe.net (207.45.221.98) [AS 6453] 4 msec 0 msec 0 m
sec
3 if-1-0.core1.Washington.Teleglobe.net (207.45.223.170) [AS 6453] 8 msec 4 
msec 8 msec
4 if-2-0-0.bb1.Washington.Teleglobe.net (207.45.221.228) [AS 6453] 8 msec 4 
msec 8 msec
5 Serial3-1-1.GW1.DCA3.ALTER.NET (157.130.39.89) [AS 701] 1356 msec 1152 mse
c 1180 msec
                                                    ^^^^^^^^^^^^^^^^^^
                                                         !!!!!!!!!!!

6 110.ATM3-0.XR1.DCA1.ALTER.NET (146.188.161.54) [AS 701] 1048 msec 1144 mse
c 1136 msec
7 195.ATM8-0-0.GW1.DCA1.ALTER.NET (146.188.161.17) [AS 701] 1172 msec 1036 m
sec 1244 msec
8 260.GW1.TCO3.customer.ALTER.NET (157.130.33.222) [AS 701] 876 msec 788 mse
c 812 msec
9 prod-334a.tco3.web.uu.net (208.243.113.236) [AS 11486] 1112 msec
[cut]



Serial3-1-1.GW1.DCA3.ALTER.NET (157.130.39.89)

__
 
Erik-Jan Bos
Manager Network Services SURFnet
The Netherlands, Europe



Current thread: