Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Mesh running only reverse-direction tests

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Mesh running only reverse-direction tests


Chronological Thread 
  • From: Aaron Brown <>
  • To: "" <>
  • Cc: Raphael Dourado <>, "" <>
  • Subject: Re: [perfsonar-user] Mesh running only reverse-direction tests
  • Date: Tue, 26 Aug 2014 12:30:09 +0000
  • Accept-language: en-US

Hey Andrew,

Unidirectionality is the default behavior to avoid redundant tests. The idea being, if your mesh has hosts A and B in it, and they’re performing tests to each other, if A runs tests from A to B, and from B to A, and B runs tests from A to B, and B to A, it’d double the number of tests that the mesh as a whole is running. If you use MaDDash, it’ll grab the results from the mesh as a whole and display them. If you’d like to have both A and B run both tests, you can set “force_bidirectional” to "1” in the test definition.

Cheers,
Aaron

On Aug 25, 2014, at 6:00 PM, Andrew Grabowski <> wrote:

Hi Raphael and List,

I also have the same problems. I have a full mesh configured and the tests are being reported as not being bi-directional. I thought it might be an issue with the bwctld and owampd limits.. But it is not... 

On top of Raphael's observations,I also notice this on my maddash dashboard. All of the boxes are half empty... (Or half full depending on how you look at it...)

Anyone have any success fixing this?




Thank you,
Andrew Grabowski



On Fri, Aug 15, 2014 at 12:16 PM, Raphael Dourado <> wrote:
Hi!

I have a set of pSPT servers configured to perform OWAMP and BWCTL tests in full-mesh, using the Mesh Configuration tool. 
The problem is that these servers end up performing only unidirectional, reverse-direction tests, as shown in the figure below, taken from on of the nodes (10.132.0.60):

<image.png>

Probably this is just some problem with my configuration files. Please find attached the following files:
  • myconf.conf and myconf.json: mesh configuration files
  • owmesh.conf: resulting owmesh of one of my nodes, after running the "generate_configuration" script 
  • agent_configuration.conf: mesh agent configuration file I'm using on each node
At first I thought it was because I enabled the "skip redundant tests" option on the agent_configuration.conf file, but then I commented it and ran the "generate_configuration" script again, but no changes were made in the owmesh file.

Best,

Raphael Augusto Dourado.





Archive powered by MHonArc 2.6.16.

Top of Page