perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

I think you may just need to be more explicit about what you want MaDDash and your tests to do. If you are defining your tests with hostnames that have both A and AAAA records, the best way to ensure maddash only looks at the one you want is to use the ipv4_only or  ipv6_only options in the test specification of your mesh (see http://docs.perfsonar.net/config_mesh.html#ipv4-only-directive and http://docs.perfsonar.net/config_mesh.html#ipv6-only-directive). This will cause maddash to generate graphs that select only traffic of the specified type and likewise for a test to be created that only tests traffic of that type.

If you do not specify those options, then the underlying tool is going to always prefer IPv6 if both endpoints in the test have v6 addresses, otherwise it will fall back to IPv4. MaDDash in that case will just ask for any result, not caring if its v4 or v6, and display/alert on whatever it gets back. It sounds like this behavior is what you are running into, so creating a couple of tests with ipv4_only and ipv6_only should get the desired result.

Hope that helps,

Andy

On May 5, 2016 at 12:54:11 PM, Brian Candler () wrote:

When I have a maddash mesh which includes hostX.example.com and
hostY.example.com, and there are only A records for those names, it runs
tests over V4 fine.

But when the names have both A and AAAA records, the tests only run on
IPv6; the IPv4 tests stop. This is seen from looking at the collected
graphs at the /toolkit/ home page. The v4->v4 and v6->v6 graphs are both
listed, but the v4->v4 data stops at the time the AAAA records were added.

(I do realise that the dashboard itself is going to have difficulty
rendering a single traffic light where there are multiple data sources,
so perhaps that's the underlying cause of this behaviour)

So my question is: is running a maddash where the same hostname has both
A and AAAA records not supported? Does this mean I need to create
separate v4 and v6 hostnames, *and* create two separate meshes (i.e. one
between the v4 interfaces and one between the v6 interfaces?) Or is
this likely to be allowed in future?

I can give some sample URLs off-list if required.

Regards,

Brian Candler.

P.S. Running latest perfsonar; these boxes auto-updated to 3.5.1