perfSONAR User Q&A and Other Discussion

[Jon Clausen <>]

Hi

Thanks for the explanation, it does make sense once you realise the 'source'
and 'destination' columns can be read in both directions.
I might argue that 'source' and 'destination' aren't entirely correct terms
to use, when the presentation is set up like this, but that's another
discussion.

Now I just need to understand how everything else works :)

br
/jon

On 2017-08-11 12:27:43 (-0700), Andrew Lake wrote:
> Hi,
> 
> As far as I can tell, the mesh is working like you expect it to, just
> perhaps the display needs some explanation. You mesh does indeed lead to
> measurements between all 4 nodes for a total of 12 tests. The way the test
> listing works though is to organize things by unique source/destination
> pairs, of which there are only 6 (12 divided by 2). For example instead of
> fi-csc-pstp01-mi1.nordu.net to de-hmb2-pstp01-mi1.nordu.net getting one row
> and de-hmb2-pstp01-mi1.nordu.net to  fi-csc-pstp01-mi1.nordu.net getting
> another row, the forward and reverse direction are collapsed into the same
> row with the arrows next to the numbers for throughput, latency and loss
> indicating the direction.
> 
> Hope that helps,
> Andy
> 
> 
> On August 11, 2017 at 7:38:56 AM, Jon Clausen 
> ()
>  wrote:
> 
> Hi
> 
> I'm working on this perfSONAR setup with 4 measurement nodes and a central
> archive, and now I could use a couple of pointers.
> 
> The nodes are installed as CentOS7 with the personar-testpoint package
> added
> (so, not installed from the 'toolkit' ISO) on physical machines with 1G
> 'management' NIC (ssh listens on this interface only) and a 10G interface
> for measurements.
> 
> Each host has a dns name for the 1G interface and another for the 10G
> interface, so the one int the danish datacenter is;
> 1g = dk-ore-pstp01.nordu.net
> 10G = dk-ore-pstp01-mi1.nordu.net
> 
> The nodes have this /etc/perfsonar/meshconfig-agent.conf
> ---
> <mesh>
> configuration_url https://psma.nordu.net/meshconfig/nordunet.json
> </mesh>
> configure_archives 1
> ---
> 
> The archive host is a VM, also installed from the CentOS7 media, with
> perfSONAR erpo and software added post install.
> Originally I had not installed the 'perfsonar-toolkit' package, because I
> was under the impression that the measurement archive would 'work' without
> it, and because I thought the dependencies brought in a number of
> "undesirable" stuff.
> After some time, I changed my mind and did install perfsonar-toolkit.
> 
> I have a 'nordunet-mesh.conf' which build_json happily transforms to:
> https://psma.nordu.net/meshconfig/nordunet.json
> 
> The nodes are getting the config from the above URL and seem to be working
> fine, but I'm not sure the MA is...
> 
> I *think* the 'mesh' described should result in measurements between all
> four nodes, leading to a total of 12 entries on the 'toolkit' page:
> 
> https://psma.nordu.net/toolkit/
> 
> What I'm seeing, however, is just six and I am going to need help to
> understand why :P
> 
> As I wrote in the other thread I'm a perfSONAR newbie, and there are huge
> gaps in my "knowledge" at this point...
> 
> I went through the steps at
> http://docs.perfsonar.net/troubleshooting_overview.html and verified that
> the basic tests work between each node and the other three.
> I have not (yet) disabled SELinux on the MA, since I figure that it would
> prevent the web ui from working completely, not 'filter' what the ui shows.
> 
> My 'hunch' is that either the 'mesh' config does not describe what I want
> it
> to, or the 'toolkit' ui config needs updating somehow - but I realise the
> issue might well be something else entirely.
> 
> Of course I'll provide additional info as necessary, but at this point I
> don't know what to look for...
> 
> Thanks in advance for any pointers
> /jon
> 
> --

> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> 
> Spam
> Not spam
> Forget previous vote


--

Attachment: signature.asc
Description: PGP signature