Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Query re: adjusting bwctl/iperf command-line switches

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Query re: adjusting bwctl/iperf command-line switches


Chronological Thread 
  • From: Brian Tierney <>
  • To: Chris Tomkins <>
  • Cc:
  • Subject: Re: [perfsonar-user] Query re: adjusting bwctl/iperf command-line switches
  • Date: Fri, 18 May 2012 14:32:43 -0700


I could not find the documentation for this either, but you can add a
"BWTosBits" line to the TESTSPEC section of your owmesh.conf file to do this.

eg, we do this:

<TESTSPEC=BWTCP_6HR>
DESCRIPTION 6 Hour TCP Throughput (iperf)
TOOL bwctl/iperf
BWTestInterval 21600
BWTestIntervalStartAlpha 25
BWReportInterval 2
BWTestDuration 20
# use ESnet scavenger service
BWTosBits 32
</TESTSPEC>





On May 18, 2012, at 9:22 AM, Chris Tomkins wrote:

> Hi,
>
> I hope I am using this soap-box appropriately. Please feel free to
> ignore me or berate me if not. Firstly, many thanks to those
> responsible for PerfSonar, it's an excellent tool.
>
> I would like to use PerfSonar to collect bandwidth/latency/jitter/loss
> statistics for some networks that have recently had QoS deployed for a
> future voice/videoconferencing network. However, in order to do so I
> would like to adjust the switches that are set when perfsonar calls
> bwctl - specifically I would like to change the DSCP/ToS settings that
> iperf uses and also the server port. I have had a good look around the
> documentation and forums, and have also dug around the filesystem and
> experimented with inotifywatch to try to catch the files being
> modified, but no luck.
>
> I would be very grateful for any help or comments - and regardless,
> many thanks for reading.
>
> Chris
>
> --
> Chris Tomkins




Archive powered by MHonArc 2.6.16.

Top of Page