UUNet->Teleglobe

Mailman List Mirror (Read Only)
1

Hello,

Do you see any issue between UUNet and TeleGlobe in
East coast?

traceroute to ix-12-0-0.bb1.HongKong.teleglobe.net
(64.86.126.18) from 195.129.70.25: 1-30 hops, 38 byte
packets
1 ge-0-0-0.ams9eusoesr1.ams.ops.eu.uu.net
(193.67.79.213) [AS702 - NLnet Pseudo blocks] 0.672
ms (ttl=254!) 0.306 ms (ttl=254!) 0.283 ms
(ttl=254!)
2 ge-1-1-0.HR1.AMS9.ALTER.NET (212.136.185.117)
[AS702 - NLnet Pseudo blocks] 0.351 ms (ttl=253!)
0.326 ms (ttl=253!) 0.299 ms (ttl=253!)
3 so-2-0-0.CR2.AMS9.ALTER.NET (212.136.185.109)
[AS702 - NLnet Pseudo blocks] 0.352 ms (ttl=252!)
0.331 ms (ttl=252!) 0.311 ms (ttl=252!)
4 so-7-0-0.XR1.AMS6.ALTER.NET (212.136.185.105)
[AS702 - NLnet Pseudo blocks] 0.395 ms (ttl=251!)
0.393 ms (ttl=251!) 0.371 ms (ttl=251!)
5 so-0-1-0.TR2.AMS2.ALTER.NET (146.188.8.82) [AS702
- UUNET-NET] 0.424 ms (ttl=250!) 0.427 ms (ttl=250!)
0.418 ms (ttl=250!)
6 so-4-0-0.IR1.DCA4.ALTER.NET (146.188.5.197) [AS702
- UUNET-NET] 82.1 ms (ttl=249!) 82.2 ms (ttl=249!)
82.1 ms (ttl=249!)
7 so-0-0-0.IL1.DCA6.ALTER.NET (146.188.13.33) [AS702
- UUNET-NET] 82.1 ms (ttl=248!) 82.1 ms (ttl=248!)
82.2 ms (ttl=248!)
8 0.so-1-0-0.TL1.DCA6.ALTER.NET (152.63.9.194) 82.2
ms (ttl=247!) 82.2 ms (ttl=247!) 82.2 ms (ttl=247!)
9 0.so-6-0-0.XL1.DCA6.ALTER.NET (152.63.38.70) 82.2
ms (ttl=246!) 82.2 ms (ttl=246!) 82.2 ms (ttl=246!)
10 POS6-0.BR3.DCA6.ALTER.NET (152.63.38.117) 82.8 ms
82.6 ms 82.6 ms
11 204.255.174.198 (204.255.174.198) 84.0 ms 84.0
ms 84.0 ms
12 if-2-0.core2.Newark.Teleglobe.net (64.86.83.213)
348 ms (ttl=236!) 348 ms (ttl=236!) 349 ms
(ttl=236!)
13 if-1-0.core3.PaloAlto.teleglobe.net
(64.86.138.125) 352 ms (ttl=237!) 353 ms (ttl=237!)
352 ms (ttl=237!)
14 if-10-0.core2.PaloAlto.Teleglobe.net
(207.45.220.6) 351 ms (ttl=237!) 351 ms (ttl=237!)
353 ms (ttl=237!)
15 if-7-0.core2.LosAngeles.Teleglobe.net
(207.45.222.25) 489 ms (ttl=239!) 384 ms (ttl=239!)
415 ms (ttl=239!)
16 if-5-0.core1.LosAngeles.Teleglobe.net
(207.45.223.62) 348 ms 348 ms 348 ms
17 if-3-0.core1.HongKong.teleglobe.net (64.86.129.5)
351 ms (ttl=241!) 351 ms (ttl=241!) 351 ms
(ttl=241!)
18 if-8-0-0.bb1.HongKong.Teleglobe.net (64.86.80.129)
352 ms (ttl=240!) 353 ms (ttl=240!) 352 ms
(ttl=240!)
19 ix-12-0-0.bb1.HongKong.teleglobe.net
(64.86.126.18) * 410 ms (ttl=241!) 410 ms
(ttl=241!)

Thanks,

-J

2

Hello,

Do you see any issue between UUNet and TeleGlobe in
East coast?

No.

10 POS6-0.BR3.DCA6.ALTER.NET (152.63.38.117) 82.8 ms
82.6 ms 82.6 ms
11 204.255.174.198 (204.255.174.198) 84.0 ms 84.0
ms 84.0 ms
12 if-2-0.core2.Newark.Teleglobe.net (64.86.83.213)
348 ms (ttl=236!) 348 ms (ttl=236!) 349 ms

First off, the actual border between UU and Teleglobe is between hops 10
and 11. Since the IP block for the /30 is owned by UU, Teleglobe probably
(either intentionally or unintentionally) did not exchange the PTR info
w/UU. You can tell this a couple of ways:

a) UU's "BR" router designation (Border Router)
b) The lack of the "ix" name on the first Teleglobe interface you see
c) 204.255.174.197 == POS2-3.BR3.DCA6.ALTER.NET

The rest, without knowing anything about Teleglobe's infrastructure in
particular, looks like a Cisco MPLS-ism. When decrementing ttl through the
lsp is turned on, you see the latency for the end of the tunnel on every
reply. Since the rtt is a) consistant for every hop afterwards, and b)
ends in a place where that rtt makes sense, it is a dead giveaway:

18 if-8-0-0.bb1.HongKong.Teleglobe.net (64.86.80.129)
352 ms (ttl=240!) 353 ms (ttl=240!) 352 ms
(ttl=240!)

Happy traceroute engineering.