User's Manual Part 2
Tech-X Flex
®
(NG2) Tech-X Flex User Guide - Firmware v06.50
6-7
Intro
Overview
Wi-Fi
Ethernet
System
IP/Video
MoCA
RF
Specs
6.5 L4 Performance Test
The L4 Performance Test is useful to verify the availability of a certain bandwidth and to determine the
maximum overall throughput. According to the test setup, it can run in either the upstream or
downstream direction.
The test uses iPerf 3.1 as the underlying technology, based in layer 4 (TCP or UDP). Therefore, the
target endpoint must be a compliant iPerf 3.1 server. The unit first establishes a “control plane”
connection with the server over TCP, then negotiates the testing setup. When primary testing begins,
either the unit or the server initiates the requested number of streams to the other endpoint. Both
endpoints analyze the traffic and maintain an identical set of results metrics. Once the primary testing is
complete, the endpoints exchange results information and then terminate all connections.
iPerf 3.1 is principally developed and maintained by third-party Energy Sciences Network (ESNet) /
Lawrence Berkeley National Laboratory. For more information on ESNet and iPerf, visit
http://software.es.net/iperf/.
6.5.1 Setup - L4 Performance Test
Table 6-6 L4 Performance Test - Setup
Parameter Description
Destination IP address or URL of the target iPerf server.
Duration Length of time to run the primary testing segment, in seconds.
TCP or UDP Specifies whether to use TCP or UDP encapsulation for the primary test
streams. Typically, TCP is the preferred option.
Streams Number of parallel TCP or UDP streams to initiate and maintain during
the primary testing segment. For a downstream test, traffic streams are
initiated by the server and received by the client, each stream on a unique
destination port. For an upstream test, the unit initiates the streams, each
on a unique source port.
Port TCP port on which the server listens for client communications. All activity
regarding the server occurs on this port; including all control plane
negotiations and test stream activity.
BW Maximum throughput to attempt, in Mbps. For TCP tests only, you can
specify 0 (zero) to test at the maximum throughput possible.
TCP Win Sz
(TCP tests only)
Window size to configure on the TCP interface of each endpoint, in bytes.
Specify 0 (zero) to allow the interfaces to negotiate and use a size based
on default interface settings.
Preliminary issue - Limited distribution only!