perfSONAR User Q&A and Other Discussion

["Uhl, George D. (GSFC-423.0)[SGT INC]" <>]

Hi Ivan,

It was an unaccounted for firewall after all.  After changing the rule and after the port 443 connection attempt fails, pScheduler tries port 4823.  My apologies for the false alarm.

Thanks,

George

From: "Garnizov, Ivan (RRZE)" <>
Date: Thursday, February 9, 2017 at 4:58 AM
To: George Uhl <>, "" <>
Cc: "" <>
Subject: RE: [perfsonar-user] perfSONAR 4.0 RC3 update

Hi Brian, George,

 

I believe George demonstrates in his email, that there was no attempt made to connect with the remote participant on any other port than 443.

This appears to be strange (unexpected) and probably we need to get more debug information.

 

Please run:

pscheduler task throughput --debug  --dest 169.154.197.28

 

to throw some more light on the incident.

 

 

Regards,

Ivan Garnizov

 

GEANT SA1T2: pS deployments GN Operations

GEANT SA2T3: pS development team

GEANT SA3T5: eduPERT team

 

 

From: [] On Behalf Of Uhl, George D. (GSFC-423.0)[SGT INC]
Sent: Mittwoch, 8. Februar 2017 19:27
To:
Cc:
Subject: Re: [perfsonar-user] perfSONAR 4.0 RC3 update

 

I tried that command but it didn’t work.  

 

$ pscheduler task throughput --dest 169.154.197.28

Submitting task...

Unable to determine the lead participant: Can't find pScheduler or BWCTL on 169.154.197.28

 

Tcpdump on the bwctld host reveals:

 

# tcpdump -i p2p1 -nn host x.107.195.203

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on p2p1, link-type EN10MB (Ethernet), capture size 65535 bytes

13:19:56.513686 IP x.107.195.203.38816 > x.154.197.28.443: Flags [S], seq 432656405, win 42340, options [mss 1460,sackOK,TS val 2602361819 ecr 0,nop,wscale 14], length 0

13:19:56.513738 IP x.154.197.28.443 > x.107.195.203.38816: Flags [R.], seq 0, ack 432656406, win 0, length 0 

13:19:57.573654 IP x.107.195.203.38816 > x.154.197.28.443: Flags [S], seq 432656405, win 42340, options [mss 1460,sackOK,TS val 2602362880 ecr 0,nop,wscale 14], length 0 

13:19:57.573704 IP x.154.197.28.443 > x.107.195.203.38816: Flags [R.], seq 0, ack 1, win 0, length 0 

13:19:59.621673 IP x.107.195.203.38816 > x.154.197.28.443: Flags [S], seq 432656405, win 42340, options [mss 1460,sackOK,TS val 2602364928 ecr 0,nop,wscale 14], length 0 

13:19:59.621724 IP x.154.197.28.443 > x.107.195.203.38816: Flags [R.], seq 0, ack 1, win 0, length 0 

^C

So if pScheduler fails to connect on 443 is it supposed to try 4823?

 

 

From: Brian Tierney <>
Reply-To: "" <>
Date: Wednesday, February 8, 2017 at 11:36 AM
To: George Uhl <>
Cc: "" <>
Subject: Re: [perfsonar-user] perfSONAR 4.0 RC3 update

 

 

It should work fine. What command are you using?

 

For example, this works from a 4.0 host to a 3.5 host:

 

pscheduler task throughput --dest receive_host

 

 

 

 

On Wed, Feb 8, 2017 at 7:19 AM, Uhl, George D. (GSFC-423.0)[SGT INC] <> wrote:

Hi,

 

I installed the perfsonar-tools package for pS 4.0 but I’m unable to get pScheduler to test with BWCTL.  I thought there were tool plugins for pScheduler to support this.  Are they available in the perfsonar-tools package?

 

Thanks,

George

 

--

Brian Tierney, http://www.es.net/tierney
Energy Sciences Network (ESnet), Berkeley National Lab
http://fasterdata.es.net