perfsonar-user - Re: [perfsonar-user] graphs for IPv6 peers stopped updating after 4.0 upgrade
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: "Curtis, Bruce" <>
- To: Bill Owens <>
- Cc: "Curtis, Bruce" <>, "" <>
- Subject: Re: [perfsonar-user] graphs for IPv6 peers stopped updating after 4.0 upgrade
- Date: Thu, 27 Apr 2017 16:58:02 +0000
- Accept-language: en-US
- Authentication-results: nysernet.org; dkim=none (message not signed) header.d=none;nysernet.org; dmarc=none action=none header.from=ndsu.edu;
- Ironport-phdr: 9a23:ajHhlB3nCF67irtksmDT+DRfVm0co7zxezQtwd8ZsesWK/jxwZ3uMQTl6Ol3ixeRBMOAuqwC17Sd6vi6EUU7or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6arXK99yMdFQviPgRpOOv1BpTSj8Oq3Oyu5pHfeQtFiT68bL9oIxi7rArdutQKjYd8N6081gbHrnxUdupM2GhmP0iTnxHy5sex+J5s7SFdsO8/+sBDTKv3Yb02QaRXAzo6PW814tbrtQTYQguU+nQcSGQWnQFWDAXD8Rr3Q43+sir+tup6xSmaIcj7Rq06VDi+86tmTgLjhTwZPDAl7m7Yls1wjLpaoB2/oRx/35XUa5yROPZnY6/RYc8WSW9HU81MVSJOH5m8YpMPAeQfIOhYs4fzqVgArRS8BAmjGOzhxTBTi3/qxqI61vgtHR3a0AEiGd8FrXTarM/yNKcXSe25wrfFzSjZb/NK2Df985DEeQ08rPGWQLJ/bdTexUcyHA7ClVqQs5HlMC+L2egXr2eb8vBgVf6ui248sAxxpCWgxtwxioXTmI0a103E+Dx/zY0oK9O4T0t7bsSlEJtWryyVKZB2TtkkQ252pCY20rkGtoW/fCQQx5QnwADfZ+SBc4iP/x3sTuWRLS1mi314ZbKznxOy8VKmyuLiSsm4ylNKoTFfntbQrH8A0QHY5MufSvZl4EuuwyqD2x3W5+1ZPEw4iK/WK5Auz7IsipYetErDETH5lUj5iaKbc0cp9vWp5uj/fLnquoOQO5JxhwzxNqkjlNCzDOE8PwUOWmWW/Pmw2KP/8UD/Xb5ElOc5krPDv5DfPckbprC2AwtS0os78xiyEzCo3MgGkXUeMVxLYA+Lg5HuO17VPv/0F/C/g0mwkDhwwPDGI7vhDYjXInjbirfheqp95FBAxwovzNBf4JRUBqsGIPLuRk/xsNvYDhg6MwCu3+nnD9B92psfWWKJHKCZLLvfvUGS6e4zPuWBYZIZtCvgJ/Ug6f7jgmM1lUMYcKmnw5QaZ3+1E/FjLkibfHbhg88NEWIQsQo/SOzqhkeCUTlWZ3uqRK08/Cw7B564AovZWo+tnaaB3Du6Hp1NfW1GDE2DEWz1d4meRfgDdT+SLtd7kjMYTbihV5Mh1Ra2uQ/i1bVnNOTU+jYftZLlztd1/fTflQwp9TNqFcSQyGWNT2BvnmMUXD86wrpzoU17ylefz6d4mfpYGsJP5/9XSAs1K4PTz/EpQ+z1DyjAetPBb0mrRM7uVTYuQ9Qq69kfeEtnHdi+yBfZ0Hz5LaUSkunBL4Eu7qPHmzDbPdt2xjyOgKM7klIrBMBSL3GnnYZ5+xPOQYPFjhPKxO6Raa0A0XuVpy+4xm2UsRQdCVYoXA==
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
> On Apr 27, 2017, at 10:17 AM, Bill Owens
> <>
> wrote:
>
> Bruce,
>
> Do the tests work if you put an IPv4 numeric address in the host box,
> instead of the name? I’ve run into what appears to be an issue with hosts
> that have both A and AAAA records, even if they’re only selected for IPv4.
>
> Bill.
I do have a test I set up a long time ago to bdw-uofm-fg.mrnet.mb.ca at
192.139.69.54, 2001:410:2000::4 that is defined with just the IPv4 number and
that continues to work. However I’m not sure that bdw-uofm-fg.mrnet.mb.ca
had an IPv6 address when I set up the test.
I see that 192.139.69.54 does not have a reverse DNS entry.
<target>
address 192.139.69.54
<override_parameters>
type bwctl
force_ipv4 1
</override_parameters>
description MRnet, Winnipeg, MB, CA
</target>
$ host 192.139.69.54
Host 54.69.139.192.in-addr.arpa. not found: 3(NXDOMAIN)
I added a new test for 131.243.246.66 ps-border1-pt.lbl.gov and that test has
been added to /etc/perfsonar/meshconfig-agent-tasks.conf
<target>
address 131.243.246.66
<override_parameters>
type bwctl
force_ipv4 1
</override_parameters>
description test LBL
</target>
But the test results do not appear on the public dashboard.
131.243.246.66 does have a reverse DNS entry
host 131.243.246.66
66.246.243.131.in-addr.arpa domain name pointer ps-border1-pt.lbl.gov.
>
> On 4/24/17, 11:44 AM,
> "
> on behalf of Curtis, Bruce"
> <
> on behalf of
> >
> wrote:
>
> We have two perfsonar boxes and after the automatic upgrade to 4.0 some
> graphs stopped updating.
>
> It looks like the common variable for the graphs that do not update is
> that perfsonar lists the IPv6 address under the host name.
>
> I verified that I can run the throughput tests manually over IPv6 with
> the pscheduler command.
>
> I do see lots of these error messages but haven’t verified that they are
> related to the problem.
>
> Apr 23 04:12:41 perfsonar2 bwctld[28704]: FILE=sapi.c, LINE=391,
> BWLControlAccept(): Unable to read ClientGreeting message
>
> These are our two hosts that exhibit the problem.
>
> https://perfsonar2.ndsu.nodak.edu
>
> https:perfsonar.ndsu.nodak.edu
>
> Deleting the tests and adding them back with IPv4 set does not seem to
> result in working graphs either.
>
>
> I also noticed the same problem on ps-border1-pt.lbl.gov to sites
> nersc-pt1-v6.es.net and bost-pt1-v6.es.net and sent email to the admin
> there and received a reply that they will add it to their list of issues to
> look into.
>>
>
> ---
> Bruce Curtis
>
> Certified NetAnalyst II 701-231-8527
> North Dakota State University
>
>
>
---
Bruce Curtis
Certified NetAnalyst II 701-231-8527
North Dakota State University
- [perfsonar-user] graphs for IPv6 peers stopped updating after 4.0 upgrade, Curtis, Bruce, 04/24/2017
- Re: [perfsonar-user] graphs for IPv6 peers stopped updating after 4.0 upgrade, Andrew Lake, 04/25/2017
- <Possible follow-up(s)>
- Re: [perfsonar-user] graphs for IPv6 peers stopped updating after 4.0 upgrade, Bill Owens, 04/27/2017
- Re: [perfsonar-user] graphs for IPv6 peers stopped updating after 4.0 upgrade, Andrew Lake, 04/27/2017
- Re: [perfsonar-user] graphs for IPv6 peers stopped updating after 4.0 upgrade, Bill Owens, 04/27/2017
- Re: [perfsonar-user] graphs for IPv6 peers stopped updating after 4.0 upgrade, Pedro Reis, 04/27/2017
- Re: [perfsonar-user] graphs for IPv6 peers stopped updating after 4.0 upgrade, Bill Owens, 04/27/2017
- Re: [perfsonar-user] graphs for IPv6 peers stopped updating after 4.0 upgrade, Curtis, Bruce, 04/27/2017
- Re: [perfsonar-user] graphs for IPv6 peers stopped updating after 4.0 upgrade, Andrew Lake, 04/28/2017
- Re: [perfsonar-user] graphs for IPv6 peers stopped updating after 4.0 upgrade, Andrew Lake, 04/27/2017
Archive powered by MHonArc 2.6.19.