Testing for Azure Bandwidth

See before customers often meet some customers ask us your azure bandwidth is how much, each answer this question we can only vaguely tell the customer a approximate value, this will leave the customer to think we are very unprofessional impression, in fact, standing in the customer's perspective, we can understand, Even such a question you can not accurately answer, how can I believe that you can help me to carry out, so I and my colleague time measured, here I focus on how to test, rather than the test results analysis!!!

Test conditions, accounts for the Azure China region

Before testing, I would like to explain to the reader a little bit about the test environment and the tools used in this test, the test tool is Iperf, the specific version is iperf3.1.3

The first step, login account, create a virtual machine, there are two ways to create, the first is created through the portal, the other is created through PowerShell, the steps to create a virtual machine here is no longer demonstrated, if there are no readers can look at my previous blog for reference, in this POC environment, We take an East Area D4 virtual machine as server side, 4 North A1 as client side, Os are centos7.2, frame composition as follows;

Here I want to say, the reason is to put the server side and client side in different regions, because if the server side and client side are in the same region, both ends of the traffic can not be out of the data center, because the data center edge gateway to receive packets, will be unpacking to view the destination IP, if the IP address is found in the data center, the Edge Gateway will directly drop the packet to the IP address of the virtual machine, so the packet can not be out of the data center, in fact, most of the network bandwidth bottlenecks are on the public Internet, not the intranet, So the author's suggestion is that if you have the best use of the local server and the virtual machine on the Azure data center to do the test, because the author lacks the local server, also more lazy to build the environment, here in the North built four virtual machine as a client, the packet directly in the connection two data center of bare fiber transmission, This is more in favor of the methodology of the display, the actual significance is small.

Build the virtual network and virtual machine according to the architecture diagram, the result is as follows

The next task is to install Iperf, we first SSH remotely to all VMS, before installing iperf we need to make sure that the virtual machine OS is already installed made and GCC, because the OS mentioned by Azure is the base version, most of us need to install it ourselves

On the server side, after we landed via SSH

Enter sudo yum install GCC to see the following results

At this point, the server side of GCC is installed successfully, then install make

Enter sudo yum install make and the results are as follows

Indicates that make already exists, no need to install

Client side operation is the same, here is no longer one by one Show

The next job is to download and unzip the Iperf source package

On the server side, enter the following command

$sudo CD/tmp$sudo wget http://downloads.es.net/pub/iperf/iperf-3-current.tar.gz$sudo Tar zxvf iperf-3-current.tar.gz

Completing the above steps will see the following results in the/tmp directory

Next Install Iperf

$sudo CD iperf-3.1.4/$sudo. /Configure$sudo make$sudo make install

After the installation is successful, Iperf is installed in the/usr/local/bin directory and you can see the following results in this directory

If Iperf run the following error

 while loading shared libraries:libiperf.so. 0 object file:no such file or directory

Input idconfig can be solved

The client side of the installation method with the server side, here is no longer detailed introduction

In this way, all the virtual machine Iperf are installed, some people can not help asking, so good, of course not, there is a very important step, is to modify the access rules, because there are firewall rules, must be modified to use IPERF for testing, testing when we want to specify Iperf Server-side monitoring port, which is set to TCP-5001, on the firewall to open the TCP-5001 port corresponding access rules, in ASM, we need to configure the endpoint, in arm, the NSG needs to be configured, because this POC environment is deployed in arm, So we need to modify the NSG, in fact, the author's advice is best to use arm, after all, arm a lot of features, some features even do not need to complete in PowerShell, directly can be done in arm.

The specific rules of modification are as follows

Add the following rule to the server-side NSG

Then we can start testing, first we enter the following command on the server side to listen for 5001 ports, output a result every two seconds;

$iperf 3-s-P 5001-i 2

See the following results, indicating that IPERF is operating normally

Next, wait for the client side to start testing, enter the following command on the client side

$iperf 3-c 139.219.229.18-p 4-t 30-i 2-p 5001

This command means that the client side concurrently 4 data streams, the test time is 30s, every 2s output a result

First we look at the client vm1, as follows

ServerD4 end results are as follows

Through the above, we can see the bandwidth around 120Mb, here I would like to remind that four client side can only take turns to test, that is, when the client vm1 in the test, the other client can not be tested, even if the input command can not be tested normally, Because the server port is in the busy state, the following appears

Here, the other client side is no longer showing, because the measured bandwidth is relatively stable, so no longer show, and finally want to remind you, because the test will incur the cost of traffic, so before testing need to be prepared

Testing for Azure Bandwidth