perfsonar-user - [perfsonar-user] incomplete tracepath graph
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: "Uhl, George D. (GSFC-423.0)[SGT INC]" <>
- To: perfsonar-user <>
- Subject: [perfsonar-user] incomplete tracepath graph
- Date: Thu, 22 Jan 2015 13:46:15 +0000
- Accept-language: en-US
When displaying traceroute/tracepath graph output, I'm not getting the complete path on a 3.4.1-1.pSPS server.
Topology beginning at Wed Jan 21 00:07:25 2015 (UTC -5)
Yet, when I run traceroute or trace path from the CLI, I do:
[uhl@perfsonar ~]$ traceroute6 2001:4200:0:5001:92e2:baff:fe20:dd70
traceroute to 2001:4200:0:5001:92e2:baff:fe20:dd70 (2001:4200:0:5001:92e2:baff:fe20:dd70), 30 hops max, 80 byte packets
1 2001:4d0:241b:1::1 (2001:4d0:241b:1::1) 0.660 ms 0.777 ms 0.771 ms
2 2001:468:c00:fffb::1 (2001:468:c00:fffb::1) 0.626 ms 0.617 ms 0.600 ms
3 2001:468:c00:c::2 (2001:468:c00:c::2) 1.331 ms 1.319 ms 1.306 ms
4 xe-0.equinix.asbnva01.us.bb.gin.ntt.net (2001:504:0:2::2914:1) 2.777 ms 2.864 ms 4.075 ms
5 ae-2.r23.asbnva02.us.bb.gin.ntt.net (2001:418:0:2000::3b9) 3.423 ms 2.367 ms 3.224 ms
6 ae-6.r23.amstnl02.nl.bb.gin.ntt.net (2001:418:0:6000::10a) 89.940 ms 92.747 ms 92.835 ms
7 ae-1.r03.amstnl02.nl.bb.gin.ntt.net (2001:728:0:2000::142) 86.238 ms 94.461 ms 94.412 ms
8 ae-3.r03.londen05.uk.bb.gin.ntt.net (2001:728:0:2000::14a) 113.813 ms 104.410 ms 93.071 ms
9 ae-5.r02.londen05.uk.bb.gin.ntt.net (2001:728:0:2000::41) 91.509 ms 98.477 ms 93.158 ms
10 xe-0-1-0-6.r02.londen05.uk.ce.gin.ntt.net (2001:728:0:5000::86) 102.485 ms 105.147 ms 104.566 ms
11 2001:43f8:20:fffa::2 (2001:43f8:20:fffa::2) 246.781 ms 243.314 ms 238.489 ms
12 te1-0-0-bfn1-pe1.tenet.ac.za (2001:4200::25) 256.579 ms 259.911 ms 248.426 ms
13 * * *
14 * * *
15 te8-4-pta1-pe1.tenet.ac.za (2001:4200::3d) 273.115 ms 272.737 ms 284.078 ms
16 2001:4200:0:5001:92e2:baff:fe20:dd70 (2001:4200:0:5001:92e2:baff:fe20:dd70) 273.683 ms 274.702 ms 273.156 ms
[uhl@perfsonar ~]$ tracepath6 2001:4200:0:5001:92e2:baff:fe20:dd70
1?: [LOCALHOST] pmtu 1500
1: 2001:4d0:241b:1::1 1.344ms
1: 2001:4d0:241b:1::1 2.344ms
2: 2001:468:c00:fffb::1 1.485ms
3: 2001:468:c00:c::2 1.605ms
4: xe-0.equinix.asbnva01.us.bb.gin.ntt.net 2.895ms
5: ae-2.r23.asbnva02.us.bb.gin.ntt.net 2.673ms
6: ae-6.r23.amstnl02.nl.bb.gin.ntt.net 93.864ms
7: ae-1.r03.amstnl02.nl.bb.gin.ntt.net 88.281ms
8: ae-3.r03.londen05.uk.bb.gin.ntt.net 95.220ms
9: ae-5.r02.londen05.uk.bb.gin.ntt.net 94.252ms
10: xe-0-1-0-6.r02.londen05.uk.ce.gin.ntt.net 102.832ms asymm 7
11: 2001:43f8:20:fffa::2 239.966ms asymm 8
12: te1-0-0-bfn1-pe1.tenet.ac.za 249.855ms asymm 9
13: no reply
14: no reply
15: te8-4-pta1-pe1.tenet.ac.za 270.805ms asymm 12
16: 2001:4200:0:5001:92e2:baff:fe20:dd70 270.725ms !A
Resume: pmtu 1500
This holds true for IPv4 as well but I'm only seeing it for tracepath/traceroute outbound from my perfsonar server. The reverse path data is displayed in total:
OUTBOUND:
Topology beginning at Wed Jan 21 10:23:35 2015 (UTC -5)
REVERSE:
Topology beginning at Wed Jan 21 14:49:47 2015 (UTC -5)
|
- [perfsonar-user] incomplete tracepath graph, Uhl, George D. (GSFC-423.0)[SGT INC], 01/22/2015
- Re: [perfsonar-user] incomplete tracepath graph, Andrew Lake, 01/22/2015
- Re: [perfsonar-user] incomplete tracepath graph, Andrew Lake, 01/22/2015
- Re: [perfsonar-user] incomplete tracepath graph, Andrew Lake, 01/22/2015
- Re: [perfsonar-user] incomplete tracepath graph, Uhl, George D. (GSFC-423.0)[SGT INC], 01/24/2015
- Re: [perfsonar-user] incomplete tracepath graph, Andrew Lake, 01/22/2015
Archive powered by MHonArc 2.6.16.