SD-WAN

nevermind wind, no matter rain

Flow Visibility (VMware SD-WAN)

Test 3: iperf3 running longer than 5-minutes

In this test3, I would like to run a single iperf3 for, say, 12 minutes. The reason is this flow will spread across multiple 5-minutes interval. The expectation is the flow will be like “chopped” to multiple 5 minutes flow data. Let’s see.

The iperf3 command being used is:

/usr/local/bin/iperf3 -c 10.230.1.230 -w 128k -b 2M -t 720

The iperf3 client screen capture:

Diagram 18: iperf3 client command in test3

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 test3:

Diagram 19: packet capture conversations at iperf client machine during test3

From the packet capture, there are 2 flows as follow:

10.2.1.111:38682 <—> 10.230.1.230:5201 (iperf3 control connection)

10.2.1.111:38694 <—> 10.230.1.230:5201

Let’s check the “Flows” tab (flow visibility) for Left-Spoke-1:

Diagram 20: Flows output generate by iperf3 in test3 in Left-Spoke-1 (left part)
Diagram 21: Flows output generate by iperf3 in test3 in Left-Spoke-1 (right part)

From the packet capture the two iperf3 flows start at 09:43:57am and end at 09:55:57am. This 12 minutes duration cross the follow four 5-minutes interval (the flow 5-minutes interval):

  • 09:39:58am to 09:33:58am
  • 09:44:58am to 09:49:59am
  • 09:49:59am to 09:54:59am
  • 09:54:59am to 09:59:59am

That’s why from the “Flows” tab, the two flows actually generate 8 rows of data (spread across 4 interval and there are 2 WAN links, so 4×2 = 8).

Flow Visibility (VMware SD-WAN)

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to top