Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Testing internet2 traceroute?

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Testing internet2 traceroute?


Chronological Thread 
  • From: Jason Zurawski <>
  • To: Pol Llovet <>
  • Cc:
  • Subject: Re: [perfsonar-user] Testing internet2 traceroute?
  • Date: Thu, 14 Aug 2014 08:28:06 -0500

web100clt will work, even if the java/http based tester is not being
maintained:

> [zurawski@bnl-pt1
> ~]$ ./web100clt -n ndt.wash.net.internet2.edu
> Testing network path for configuration and performance problems -- Using
> IPv6 address
> Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
> checking for firewalls . . . . . . . . . . . . . . . . . . . Done
> running 10s outbound test (client to server) . . . . . 808.36 Mb/s
> running 10s inbound test (server to client) . . . . . . 982.90 Mb/s
> The slowest link in the end-to-end path is a 1.0 Gbps Gigabit Ethernet
> subnet
> Information: Other network traffic is congesting the link
> Server 'ndt.wash.net.internet2.edu' is not behind a firewall. [Connection
> to the ephemeral port was successful]
> Client is probably behind a firewall. [Connection to the ephemeral port
> failed]
> Packet size is preserved End-to-End
> Information: Network Address Translation (NAT) box is modifying the
> Server's IP address
> Server says [2001:468:9:11::16:3] but Client says [
> eth-1.nms-rexp.wash.net.internet2.edu]
> Information: Network Address Translation (NAT) box is modifying the
> Client's IP address
> Server says [2001:400:6401:1150::3] but Client says [
> bnl-pt1-v6.es.net]

Thanks;

-jason

On Aug 14, 2014, at 8:23 AM, Aaron Brown
<>
wrote:

> One thing that you may be able to do is to have someone at WVSU try running
> an NDT test to http://nms-rexp.wash.net.internet2.edu:7123/ . I *think*
> that host is still up, but I’m not positive.
>
> Cheers,
> Aaron
>
> On Aug 14, 2014, at 9:19 AM, Aaron Brown
> <>
> wrote:
>
>> Hey Pol,
>>
>> Would it be possible to get someone to install either bwctl, or to stand
>> up a perfSONAR Toolkit LiveCD at WVSU? Preferably, somewhere close to the
>> campus edge.
>>
>> Cheers,
>> Aaron
>>
>> On Aug 13, 2014, at 6:30 PM, Pol Llovet
>> <>
>> wrote:
>>
>>> 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



Archive powered by MHonArc 2.6.16.

Top of Page