Need help from UUNet's routing specialist!
Hello! 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. 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 msec 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 msec 1180 msec ^^^^^^^^^^^^^^^^^^ !!!!!!!!!!! 6 110.ATM3-0.XR1.DCA1.ALTER.NET (146.188.161.54) [AS 701] 1048 msec 1144 msec 1136 msec 7 195.ATM8-0-0.GW1.DCA1.ALTER.NET (146.188.161.17) [AS 701] 1172 msec 1036 msec 1244 msec 8 260.GW1.TCO3.customer.ALTER.NET (157.130.33.222) [AS 701] 876 msec 788 msec 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) ---------------- Have a nice day! Esakov Dmitriy, Macomnet Internet Dpt.
We saw this again today also... nails in the coffin...
Hello! 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.
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 msec 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 msec 1180 msec ^^^^^^^^^^^^^^^^^^ !!!!!!!!!!!
6 110.ATM3-0.XR1.DCA1.ALTER.NET (146.188.161.54) [AS 701] 1048 msec 1144 msec 1136 msec 7 195.ATM8-0-0.GW1.DCA1.ALTER.NET (146.188.161.17) [AS 701] 1172 msec 1036 msec 1244 msec 8 260.GW1.TCO3.customer.ALTER.NET (157.130.33.222) [AS 701] 876 msec 788 msec 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)
---------------- Have a nice day! Esakov Dmitriy, Macomnet Internet Dpt.
-- Neil J. McRae - Alive and Kicking. neil@DOMINO.ORG
On Fri, 10 Dec 1999, Neil J. McRae wrote:
We saw this again today also... nails in the coffin...
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.
For the record, is anyone seeing even vaguely decent connectivity via teleglobe? It seems that 50% of the times customers complain they have a poor connection to our network, it turns out that they're going via teleglobe at some point! Are they running a 2400baud modem with a flaky fuse as their main connection or something? -- Patrick Evans - Sysadmin, bran addict and couch potato pre at pre dot org www.pre.org/pre
participants (3)
-
Dmitry S. Esakov
-
Neil J. McRae
-
Patrick Evans