perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi George,

Thanks for the logs. I think i found a bug in the tracepath parser. Could you download the attached patch file and run?

cd /opt/perfsonar_ps/regular_testing

patch -p2 < tracepath-parsing.patch

/sbin/service/regular_testing restart

Let it sit for awhile and presumably the next time the problematic tracepaths run you will get the full path.

Thanks,

Andy

Attachment: tracepath-parsing.patch
Description: Binary data

On Jan 22, 2015, at 8:46 AM, "Uhl, George D. (GSFC-423.0)[SGT INC]" <> wrote:

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)

Hop	Router	IP	Delay	MTU
7	requestTimedOut	requestTimedOut
10	xe-0-1-0-6.r02.londen05.uk.ce.gin.ntt.net	2001:728:0:5000::86	102.580ms	1500
11	2001:43f8:20:fffa::2	2001:43f8:20:fffa::2	235.776ms	1500
12	te1-0-0-bfn1-pe1.tenet.ac.za	2001:4200::25	249.830ms	1500
13	requestTimedOut	requestTimedOut
14	requestTimedOut	requestTimedOut
15	te8-4-pta1-pe1.tenet.ac.za	2001:4200::3d	270.751ms	1500
16	2001:4200:0:5001:92e2:baff:fe20:dd70	2001:4200:0:5001:92e2:baff:fe20:dd70	270.613ms	1500

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)

Hop	Router	IP	Delay	MTU
6	atla-pt1.es.net	198.124.238.18	14.128ms	1500

REVERSE:

Topology beginning at Wed Jan 21 14:49:47 2015 (UTC -5)

Hop	Router	IP	Delay	MTU
1	atlacr5-atlapt1.es.net	198.124.238.17	1.33ms
2	washcr5-ip-a-atlacr5.es.net	134.55.42.70	14.005ms
3	max-washcr5.es.net	198.124.192.94	13.244ms
4	ae0.clpk-core.maxgigapop.net	206.196.178.81	14.022ms
5	gsfc-uhl-rtr.maxgigapop.net	206.196.177.142	14.731ms
6	perfsonar.eos.nasa.gov	169.154.197.26	14.084ms