|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: Does Teleglobe implements QoS ?
Hi, Another strange thing is that Teleglobe passes packets coming via AS8342 the same way as you showed with Teleglobe's IP addresses. It is a trace from my office. [lost]:[2:01:17pm][pts/1]%[~]> traceroute 204.71.127.3 traceroute to 204.71.127.3 (204.71.127.3), 30 hops max, 38 byte packets 1 jam-4-e0-0.zenon.Net (195.2.69.65) 1.887 ms 1.115 ms 1.931 ms 2 m9-2-atm3-0-9-2-103.zenon.Net (195.2.73.221) 2.016 ms 2.043 ms 2.017 ms 3 m9-3-fa1-1-0-90.zenon.Net (195.2.70.3) 10.886 ms 5.206 ms 6.356 ms 4 m3-bvi-1.msk-m9.RosTelecom.net (195.161.2.133) 3.760 ms 7.434 ms 3.860 ms 5 c1-s0-1-0.NewYork.RosTelecom.Net (195.161.161.162) 124.627 ms 135.079 ms 212.080 ms 6 if-2-0-0.bb6.NewYork.Teleglobe.net (207.45.205.29) 124.108 ms 138.293 ms 134.732 ms 7 if-6-0-0.bb1.NewYork.Teleglobe.net (207.45.221.67) 124.241 ms 124.444 ms 128.004 ms 8 Serial0-1-0.GW2.NYC2.ALTER.NET (157.130.4.165) 159.963 ms 128.290 ms 157.130.5.217 (157.130.5.217) 131.942 ms 9 144.ATM2-0.XR2.EWR1.ALTER.NET (146.188.178.158) 146.279 ms 139.127 ms 156.021 ms 10 192.ATM3-0.TR2.EWR1.ALTER.NET (146.188.176.86) 138.311 ms 128.993 ms 147.531 ms 11 105.ATM6-0.TR2.DCA8.ALTER.NET (146.188.138.173) 273.422 ms 244.176 ms 240.139 ms 12 152.63.32.209 (152.63.32.209) 125.812 ms 126.926 ms 147.801 ms 13 192.ATM6-0.GW5.TCO1.ALTER.NET (146.188.162.165) 137.129 ms 124.777 ms 143.391 ms 14 intrepid-gw2.customer.ALTER.NET (157.130.36.214) 242.036 ms 258.814 ms 244.446 ms 15 office-shep.intrepid.net (209.190.129.38) 238.867 ms 250.612 ms 243.025 ms 16 intrepid.net (204.71.127.3) 288.863 ms 243.229 ms 237.784 ms [lost]:[2:01:25pm][pts/1]%[~]> "Dmitry S. Esakov" wrote: > > Hello! > > Macomnet (ISP, AS8470, Moscow, Russia) uses world connectivity via > Teleglobe. We have a router, managed by us, in NY. The interface pointing > to America uses Teleglobe's address and another one, pointing to Moscow > - ours. > > Regullary I see a quite strange heavy delays on Teleglobe to > Alternet interconnect point. I traced the route to several > destinations with SRC addresses from Teleglobe's and Macomnet's IP blocks. > The problem is that packets with SRC from Teleglobe address space passes > through with lower delays than packets with Macomnet's SRC addresses. > > The first thing what people expect is assymetric routing (i.e. route from > Alternet goes another way back to us). But it's not possible. Our backup > provider (AS8342) plugs into Teleglobe also. So Teleglobe advertises the > right route to Alternet and it's quite impossible for Alternet to have > another route to Macomnet. I believe it's not a routing problem. > > I contacted Teleglobe and they said that it could be a temporary > congestion. I wonder how could congestion exist for Macomnet addresses > and not to appear for Teleglobe itself!!! That is the question. > > Look at the traces below. The first one uses Teleglobe SRC address, the > second - ours. > > ----------------------------------------- > Trace with Teleglobe_SRC_ADDRESS : > ----------------------------------------- > nyy-1#trace > Protocol [ip]: > Target IP address: 204.71.127.3 > Source address: 207.45.205.14 > ^^^^^^^^^^^^^^^^^ > Teleglobe's address > Numeric display [n]: > Timeout in seconds [3]: > Probe count [3]: > Minimum Time to Live [1]: > Maximum Time to Live [30]: > Port Number [33434]: > Loose, Strict, Record, Timestamp, Verbose[none]: > Type escape sequence to abort. > Tracing the route to intrepid.net (204.71.127.3) > > 1 if-0-1-0.bb6.NewYork.Teleglobe.net (207.45.205.13) [AS 6453] 0 msec 4 msec 0 msec > 2 if-6-0-0.bb1.NewYork.Teleglobe.net (207.45.221.67) [AS 6453] 0 msec 0 msec 4 msec > 3 Serial0-1-0.GW2.NYC2.ALTER.NET (157.130.4.165) [AS 701] 0 msec 4 msec > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Teleglobe goes fine. > 157.130.5.217 [AS 701] 4 msec > 4 144.ATM2-0.XR2.NYC1.ALTER.NET (146.188.178.150) [AS 701] 4 msec 0 msec 4 msec > 5 194.ATM3-0.TR2.NYC1.ALTER.NET (146.188.178.198) [AS 701] 0 msec 4 msec 0 msec > 6 104.ATM7-0.TR2.DCA8.ALTER.NET (146.188.138.169) [AS 701] 8 msec 4 msec 12 msec > 7 152.63.32.217 [AS 701] 4 msec 8 msec 8 msec > 8 192.ATM6-0.GW5.TCO1.ALTER.NET (146.188.162.165) [AS 701] 8 msec 8 msec 8 msec > 9 intrepid-gw2.customer.ALTER.NET (157.130.36.214) [AS 701] 20 msec 20 msec 32 msec > 10 office-shep.intrepid.net (209.190.129.38) [AS 6359] 20 msec 20 msec 28 msec > 11 intrepid.net (204.71.127.3) [AS 6359] 20 msec 16 msec 20 msec > > ---------------------------------------------------- > AT THE SAME TIME Trace with Macomnet_SRC_ADDRESS : > ---------------------------------------------------- > > nyy-1#trace > Protocol [ip]: > Target IP address: 204.71.127.3 > Source address: 195.128.65.33 > ^^^^^^^^^^^^^^^^^^^ > Macomnet's address > Numeric display [n]: > Timeout in seconds [3]: > Probe count [3]: > Minimum Time to Live [1]: > Maximum Time to Live [30]: > Port Number [33434]: > Loose, Strict, Record, Timestamp, Verbose[none]: > Type escape sequence to abort. > Tracing the route to intrepid.net (204.71.127.3) > > 1 if-0-1-0.bb6.NewYork.Teleglobe.net (207.45.205.13) [AS 6453] 0 msec 0 msec 4 msec > 2 Teleglobe.net (207.45.221.99) [AS 6453] 0 msec 0 msec 0 msec > 3 * Serial0-1-0.GW2.NYC2.ALTER.NET (157.130.4.165) [AS 701] 1248 msec > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > !!!!!! > 157.130.5.217 [AS 701] 1276 msec > 4 144.ATM2-0.XR1.EWR1.ALTER.NET (146.188.178.146) [AS 701] 1220 msec 1268 msec * > 5 * * * > 6 * * 105.ATM6-0.TR1.DCA8.ALTER.NET (146.188.138.121) [AS 701] 1272 msec > 7 152.63.32.201 [AS 701] 1284 msec 1288 msec * > 8 * 193.ATM6-0.GW5.TCO1.ALTER.NET (146.188.162.169) [AS 701] 2716 msec * > 9 intrepid-gw2.customer.ALTER.NET (157.130.36.214) [AS 701] 1392 msec * 1356 msec > 10 office-shep.intrepid.net (209.190.129.38) [AS 6359] 1244 msec 1244 msec 1328 msec > 11 intrepid.net (204.71.127.3) [AS 6359] 1284 msec 1324 msec 1392 msec > > ---------------- > Have a nice day! > Esakov Dmitriy, Macomnet Internet Dpt. -- Victor L. Belov ZENON N.S.P. +7 095 250 4629
|