2-12
RedMAX Administration and Maintenance Guide
Redline Communications Inc. Confidential and Proprietary
The first step is to decide on your test scenario. For example, if you want to measure
overall sector capacity, you should provision a service flow with a maximum rate well
above what you expect to achieve. If you plan to test the throughput of a given service
package, you should ensure that your subscriber unit is provisioned using the service flow
in question. Either way, once you have completed provisioning your subscriber unit, you
should first perform a basic connectivity test, using ping as outlined in “Using the Ping
Utility” on page 2-10.
Once you have verified connectivity between the devices, you can proceed with one of the
iperf tests as described below. Ensure that the server is started first, and then the test is
initiated from the client. The server does not have to be restarted between tests unless the
nature of the test is to be modified. The server and client devices will change depending
on the test that you running. Details of which devices should be configured as the client
and as the server are provided for each test.
Depending on the system characteristic to be tested, you will use on of the following tests:
Downlink TCP Throughput
For this test, the computer connected to the subscriber unit is configured as the server.
Step 1
Open a console window on the computer behind the subscriber unit:
Table 2-4
iPerf Options
Flag
Description
i
This argument specifies the interval at which iperf will output an update of the current
measured throughput. Without this argument, iperf will only display a summary at the end
of the test.
t
This argument defines the duration of the test. It is measured in seconds. Generally, 30
seconds is recommended as a minimum.
u
This argument specifies UDP traffic. Without this argument, iperf will use TCP
b
This argument is used with the -u argument. It specifies the rate at which to pass UDP
packets. Specifying the argument automatically implies the -u argument.
d
This argument specifies that iperf should perform a bidirectional test; throughput
performance is measured in both the uplink and downlink simultaneously. It is not
recommended that this argument be used with TCP tests.
P
This argument is used to specify the number of parallel streams to be used for a given test.
If you are trying to simulate multiple customers, or multiple network applications in use
simultaneously, you can specify how many with this argument.
w
This is used to specify the TCP window size to be used by the TCP stack. The default
Windows window size is 8k. You will need to need to specify 64k TCP window for TCP tests
on both client and server by adding the "-w 64k" argument
This argument is not relevant for UDP tests.
s
This specifies that iperf will run as a server.
c
This specifies that iperf will run as a client.
