Test 2: iperf3 with simultaneous data flow
The test2 is to have iperf3 with 5 data flows running in parallel, this is used to confirm is that multiple flow with different source ports but same source IP, destination IP, destination port are being combined.
The iperf3 command being used is:
/usr/local/bin/iperf3 -c 10.230.1.230 -w 128k -P 5 -b 5M -t 30The iperf3 client screen capture:
While the iperf3 is running, packet capture was done on the iperf client machine (10.2.1.111). The following is the conversation of the packet capture during test2:
From the packet capture, there are 6 flows as follow:
- 10.2.1.111:35362 <—> 10.230.1.230:5201 (iperf3 control connection)
- 10.2.1.111:35368 <—> 10.230.1.230:5201
- 10.2.1.111:35378 <—> 10.230.1.230:5201
- 10.2.1.111:35390 <—> 10.230.1.230:5201
- 10.2.1.111:45072 <—> 10.230.1.230:5201
- 10.2.1.111:45082 <—> 10.230.1.230:5201
Let’s check the “Flows” tab (flow visibility) for Left-Spoke-1:
Again, the output is too width so the output is separated to two screen capture. Red square bracket also added to indicated the flow related to iperf3 generated under test2. The related flows only comes with two rows. It is because one row is for WAN link of GE3 while the other row is for WAN link of GE4. From this test2, we can confirm the source port is not in the consideration to listing as a separate flow in this flow visibility. That is there are in total of 6 flows, because the source IP, destination IP and destination port are the same, even the source port are different, these 6 flows are consolidated to two entries in this case due to there are two WAN links. If there is only single WAN link, we expect the flows will consolidate to a single entry.