perfSONAR User Q&A and Other Discussion

[Pol Llovet <>]

Nope!  We haven't seen any additional movement on this.  The last bit of information was the testing to the OSU endpoint. To recap: throughput to OSU is symmetrically bad, but not as bad as the asymmetric throughput to WVSU.  Throughputh to wash.net.internet2.edu looks good as the last "known good" hop on the trace.  

Not sure where to go next, actually.  This is just itch-scratching since I don't need to ship data to WVSU, and our network looks ok (this appears to be an OAR/WVSU problem).  I'd be curious to find out what's wrong (and so, presumably, would WVSU), but it's not critical.

thanks for checking up,

pol

Pol M. Llovet
Research Computing CI / Middleware

XSEDE Campus Champion

Montana State University
w: 406-994-3416
c: 406-646-6747

On Tue, Aug 12, 2014 at 7:49 PM, John Hicks <> wrote:

Hi Pol,

Has there been any movement on this?  Was anyone able to stand up an iperf server (or other) closer to WVSU edge?  Please let me know if I can provide and more help on the Internet2 end.

Thanks,

-John

On Aug 5, 2014, at 6:24 AM, Pol Llovet <> wrote:

Hi, we are diagnosing a slow throughput situation to West Virginia. All the tests through to the Washington DC internet2 PS node look good (bwctl.wash.net.internet2.edu).  I would like to test from that node through to the endpoint.  

The endpoint is just a workstation IP, and there aren't any perfsonar nodes on-campus that I can test against.  I was thinking I could just do a traceroute/ping test from the node UI, but it doesn't have the UI exposed for testing (that I could find).  And since I don't have a PS endpoint at one end, I can't use the bw* cli tools.

Any tips on how I could diagnose the rest of this issue?

Pol M. Llovet
Research Computing / Middleware

Montana State University
w: 406-994-3416
c: 406-646-6747