perfSONAR User Q&A and Other Discussion

["Garnizov, Ivan" <>]

Hi John-Paul,

 

The perfSONAR suite does not apply restrictions on usage of hostnames. All you need is to make sure that each testing server you have is capable of RESOLVING the correct IP addresses (the visible ones) of the rest servers in the testing environment.

 

It seems also that you might be in the confusing situation, which applies to multi-homed servers, where special routing assignments must be set in order to provision the perfSONAR services on all interfaces simultaneously. Is that what you are trying to achieve?

 

From your explanation it does not become clear:

• if these two hosts have real IP addresses or just private
• if these hosts are being successfully resolved to the respective IPs correctly or not for each server.
• which server is used to assign the measurements (assuming you are using the web interface)

 

Thus it is hard to answer the questions in your email!

 

 

Please also apply relevant information from the owamp/bwctl log file, which generally is /var/log/perfsonar/owamp_bwctl.log

 

Best regards,

Ivan

 

 

 

-----Original Message-----
From: [] On Behalf Of John-Paul Robinson
Sent: Thursday, July 10, 2014 5:43 AM
To:
Subject: [perfsonar-user] using a hostname instead of IP address in bwctl tests

 

Hi,

 

I'm trying to configure a perfsonar test environment and am having a hard time determining how to get my nodes to refer to each other by DNS name rather than IP address.

 

I have two nodes on different private networks and allow_internal_addresses is set on both.

 

My first node is configured by DHCP for it's IP and hostname.  It reflects its correct hostname in the /toolkit UI.  This node sits behind a firewall that exposes it's "public" IP to other nodes in the fabric.

My second node, which happens to be statically IP assigned, sits on another internal network.

 

The two nodes can reach each other when the using the correct destination IP addresses. (What about reaching each other by hostnames)  For example, when the second node uses the first nodes hostname which resolves to it's public IP and not the IP it uses behind the firewall.

 

My first node is set up to run scheduled throughput tests with the second node.  The node1->node2 tests succeed and data is being gathered for the tests.  However the node2->node1 reverse test that is triggered to run on node2 fails because it is being told to use node1's behind-the-firewall address.

 

 

I can't seem to find the documentation I need so the bwctl test scheduler tells node2 to use the DNS of node1 as the target address instead of the unreachable, behind-the-firewall IP address.

 

Is there such a configuration?

 

How could I be missing something that seems to be such an obvious config?

 

Thanks,

 

~jpr