perfSONAR User Q&A and Other Discussion

[Brian Tehan <>]

Hello,

 

I’ve been working my way through getting bandwidth tests to run at specific times each day and have been successful in doing so with the --repeat-cron flag on CLI commands (can’t do that via PWA or psconfig).  However, I’m struggling to get CLI tests to show up in a throughput mesh in MaDDash.  I’ve tried archiving to Esmond directly via /usr/share/pscheduler/psc-archiver-esmond.json and using http, with commands like the following:

 

pscheduler task --archive @/usr/share/pscheduler/psc-archiver-esmond.json --slip PT1H --sliprand --repeat-cron "0 0-5 * * 0-6" throughput --source 162.127.1.5 --dest 162.127.1.1 --duration PT30S --bandwidth 41943040 --ip-version 4 --omit PT5S

 

 

pscheduler task --archive '{"archiver": "esmond","data":{"url":http://162.127.1.5/esmond/perfsonar/archive/,"_auth-token": "<<redacted>>"}}' throughput --source 162.127.1.5 --dest 162.127.1.1 --duration PT30S --bandwidth 62914560 --ip-version 4 --omit PT5S

 

(token pulled from /usr/share/pscheduler/ psc-archiver-esmond.json)

 

 

Result data will show up on the test results graph (either by clicking on the maddash mesh square or via the main toolkit page) for each of these tests, but the mesh will still show that it’s unable to find test data, even after the next check interval has passed.  I’ve attached my pSConfig JSON that I use to make latencybg tests.  Those tests run successfully, and the results show up in the loss mesh.  Anyone have any suggestions on what I should be doing differently?

 

 

Thanks!

 

 

Brian Tehan

Regional Network Engineer

University of Nebraska System

EAB009F 6001 Dodge St

Omaha, NE 68182-0051

Office: (402) 554-6428

 

 

Attachment: latency.json
Description: latency.json

Attachment: maddash.yaml
Description: maddash.yaml