[英]Weird Google Compute Engine routing within US
We are seeing some very weird routing/latency issue for GCE within the US: 我们在美国看到GCE的一些非常奇怪的路由/延迟问题:
$ traceroute fixdemo.fxcorporate.com
traceroute to fixdemo.fxcorporate.com (204.8.241.23), 30 hops max, 60 byte packets
1 216.239.43.216 (216.239.43.216) 0.824 ms 216.239.46.192 (216.239.46.192) 0.822 ms 72.14.233.134 (72.14.233.134) 1.296 ms
2 216.239.43.216 (216.239.43.216) 1.274 ms 216.239.46.192 (216.239.46.192) 0.976 ms 64.233.174.94 (64.233.174.94) 1.272 ms
3 216.239.49.32 (216.239.49.32) 1.271 ms 64.233.174.94 (64.233.174.94) 1.261 ms 1.260 ms
4 216.239.49.24 (216.239.49.24) 1.244 ms 216.239.46.190 (216.239.46.190) 2.066 ms 216.239.43.216 (216.239.43.216) 1.243 ms
5 72.14.233.134 (72.14.233.134) 1.236 ms 1.235 ms 216.239.46.192 (216.239.46.192) 1.216 ms
6 216.239.46.192 (216.239.46.192) 1.212 ms 216.239.43.218 (216.239.43.218) 0.788 ms 64.233.174.94 (64.233.174.94) 0.824 ms
7 216.239.49.24 (216.239.49.24) 0.829 ms 216.239.43.216 (216.239.43.216) 0.781 ms 216.239.49.32 (216.239.49.32) 0.838 ms
8 216.239.43.216 (216.239.43.216) 0.837 ms 64.233.174.94 (64.233.174.94) 1.045 ms 216.239.43.216 (216.239.43.216) 0.848 ms
9 72.14.238.107 (72.14.238.107) 15.354 ms 15.389 ms 209.85.241.23 (209.85.241.23) 13.589 ms
10 72.14.237.131 (72.14.237.131) 13.596 ms 13.599 ms 13.587 ms
11 209.85.254.121 (209.85.254.121) 13.594 ms 11.643 ms 13.533 ms
12 * * *
13 ae4.cr1.ord2.us.above.net (64.125.28.49) 14.256 ms 13.891 ms 11.877 ms
14 ae0.cr2.ord2.us.above.net (64.125.20.246) 13.883 ms 13.975 ms 12.056 ms
15 ae6.cr2.lga5.us.above.net (64.125.24.29) 38.438 ms 40.585 ms 40.586 ms
16 ae3.er4.lga5.us.above.net (64.125.31.246) 42.630 ms 42.603 ms 41.923 ms
17 208.185.12.62.IPYX-065351-ZYO.above.net (208.185.12.62) 215.528 ms 216.819 ms 216.719 ms
18 fixdemo.fxcorporate.com (204.8.241.23) 216.402 ms 216.298 ms 216.474 ms
Source is located in us-central1-a, destination in New York. 源位于纽约的us-central1-a中。 Still, we see a latency via traceroute
and mtr
of > 200 ms, which starts within the above.net network. 不过,我们发现通过traceroute
和mtr
的延迟大于200毫秒,该延迟始于上述.net网络。 The same problem exists for a source in the europe-west1-a zone. Europe-west1-a区中的一个源也存在相同的问题。 I guess this is the result of some heavily asymmetric routing starting at hop #17. 我猜这是从第17跳开始的一些严重不对称路由的结果。
Any idea how to solve this? 任何想法如何解决这个问题?
you could be right, as you know it is not simple to troubleshoot routing problems, and not much can be done on the internet user side. 您可能是对的,因为您知道对路由问题进行故障诊断并不容易,并且在Internet用户端无法完成很多工作。
I would like to share this well done document about troubleshooting with Traceroute: 我想分享这份有关Traceroute故障排除的出色文档:
https://www.nanog.org/meetings/nanog45/presentations/Sunday/RAS_traceroute_N45.pdf https://www.nanog.org/meetings/nanog45/presentations/Sunday/RAS_traceroute_N45.pdf
Regards Paolo 问候保罗
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.