perfSONAR User Q&A and Other Discussion

["Uhl, George D. (GSFC-423.0)[SGT INC]" <>]

Hi Andy,

The command you gave me worked and the reverse tests are running on the non-agent node.  I checked the test result url and the test failed - at least on the non-agent hosts I checked.  It might be a firewall block on the non-agent side although I suspect that the non-agent hosts are more open than that.  I’ll do some more digging.  Your information was very helpful.

Thanks,

George

#pscheduler result https://perf-scidmz-data.cac.washington.edu/pscheduler/tasks/4e8d8190-2644-4d27-9ccf-64e503474d3d/runs/30008ed3-873c-4037-a3c3-7ed6257f2496

2019-02-22T20:26:52Z on perf-scidmz-data.cac.washington.edu with traceroute:

trace --dest enpl-pt2-10g.eos.nasa.gov --ip-version 4 --length 40 --probe-type udp --source perf-scidmz-data.cac.washington.edu --source-node perf-scidmz-data.cac.washington.edu --hops 30 --wait

  PT60S

Run failed.

Diagnostics from perf-scidmz-data.cac.washington.edu:

    (No diagnostics)

#

From: Andrew Lake <>
Date: Friday, February 22, 2019 at 11:11 AM
To: George Uhl <>, "" <>
Subject: Re: [perfsonar-user] Missing non-agent->agent traceroute tests in mesh

Hi George,

I suspect they may be getting scheduled, it just may not be as obvious given how “single-ended” tests like traceroute work. 

First thing though, I assume both ends of the test have pScheduler running given that you said throughput tests work fine? Obviously only one end has psconfig reading your mesh (hence the no-agent for the far-end) but the far-end needs pScheduler so it can kick-off the reverse test so psconfig has a way to ask for the traceroute. I am guessing both ends have it in your case, but always good to double-check.

Assuming the both have it, the traceroutes only appear in the pScheduler schedule on the source node of the test. Thus if you run “pscheduler schedule —filter-test=trace” on the node where it is the destination you won’t see it. Since traceroute doesn’t need a daemon brought up and uses a negligible amount of resources, the two pScheduler instances don’t talk to each other when the task is created (as opposed to throughput) so the task doesn’t show up on both ends. 

If you run "pscheduler schedule --filter-test trace --host FAR_END_ADDRESS” where you replace FAR_END_ADDRESS with the address of the host that should be kicking off the traceroute, you should hopefully see it.

Thanks,

Andy

On February 21, 2019 at 3:33:43 PM, Uhl, George D. (GSFC-423.0)[SGT INC] () wrote:

Hi,

I have a set of managed testpoints that are in a mesh with no-agent nodes.  I have a situation where reverse traceroutes are not getting scheduled when the no-agent nodes are the source – despite the fact that that forward traceroutes run fine with the managed node as the source.  I can’t find any consistency in the psconfig-pscheduler logs that point to an obvious cause.  I’m not having these issues with throughput tests between the same managed node/no-agent pairs.

Using “psconfig scheduler-tasks”, I see that the reverse traceroute test specifications are getting downloaded from the psconfig template.  However, when I run “pscheduler schedule —filter-test=trace” I only get the forward traceroutes.  What checks are performed by psconfig-pscheduler-agent that would drop the reverse traceroutes ?

Thanks,

George

-- 
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user