qos_project
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
qos_project [2017/11/30 18:48] – [Extracts] samer | qos_project [2017/11/30 19:01] – [6. [CO2] Implementing the Applications and Tools] samer | ||
---|---|---|---|
Line 158: | Line 158: | ||
</ | </ | ||
- | ===== -. [CO2] Implementing the Applications and Tools ===== | ||
- | In order to describe and analyze the basic steps for installing and using the tools and client/ | ||
- | |||
- | Let's start with the application iperf: | ||
- | |||
- | - To activate iperf3: | ||
- | * On the server side: iperf3 -s | ||
- | * On the client side: iperf3 -c 192.168.200.192 | ||
- | |||
- | - To visualize UDP trafic with a specific bandwidth: | ||
- | * On the client side: iperf3 -c 192.168.200.192 -u -b 2M | ||
- | Here we set the bandwidth with UDP to 2Mbit/s. | ||
- | Note that by default ,UDP sets the bandwidth to 1Mbit/s | ||
- | |||
- | - To extend the transmission time(second) as well as the number packets sent: | ||
- | * On the Client side: iperf3 -c 192.168.200.192 -t 15 | ||
- | Note that by default, iperf3 sets the time to 10 seconds | ||
- | |||
- | - To reverse mode(server sends, client receives): | ||
- | * On the Client side: iper3 -c 192.168.200.192 -R | ||
- | |||
- | - To end multiple flows: | ||
- | * On the Client side: iper3 -c 192.168.200.192 -P 2 -t 60 | ||
- | |||
- | Here we are sending 2 flows in 1 min(60 seconds) | ||
- | Note that we need to extend more the tx time in order to have similar throughput for the 2 flows so that we don't consider it as a fairness issue. | ||
- | |||
- | Let's analyze flent application: | ||
- | * On the Server side: netserver & | ||
- | -To visualize one TCP stream: | ||
- | * On the Client side: flent tcp_upload -p totals -l 60 -H 192.168.200.192 -t title2 -o test2.png | ||
- | -To visualize 12 TCP streams: | ||
- | * On the Client side: flent tcp_12up -p totals -l 60 -H 192.168.200.192 -t title3 -o test3.png | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | ===== Extracts ===== | ||
The two routers allocate IP addresses using DHCP. In order to facilitate the usage of the platform, fixed allocations are configured for the end hosts. This is configured in ''/ | The two routers allocate IP addresses using DHCP. In order to facilitate the usage of the platform, fixed allocations are configured for the end hosts. This is configured in ''/ | ||
Line 249: | Line 202: | ||
192.168.200.0/ | 192.168.200.0/ | ||
</ | </ | ||
+ | ===== -. [CO2] Implementing the Applications and Tools ===== | ||
+ | In order to describe and analyze the basic steps for installing and using the tools and client/ | ||
+ | |||
+ | Let us start with the application iperf. In the following, we present a short tutorial on the main functions of the perf tool. | ||
+ | |||
+ | * To launch iperf3: | ||
+ | * On the server side: '' | ||
+ | * On the client side: '' | ||
+ | |||
+ | * by default, the trafic sent by iperf uses TCP. In order to send UDP trafic with a specific bandwidth: | ||
+ | * On the client side: iperf3 -c 192.168.200.192 -u -b 2M | ||
+ | |||
+ | Here we set the bandwidth with UDP to 2Mbit/s. Note that by default, UDP sets the bandwidth to 1Mbit/s. | ||
+ | |||
+ | * To extend the transmission time(second) as well as the number packets sent: | ||
+ | * On the Client side: '' | ||
+ | |||
+ | Note that by default, iperf3 sets the time to 10 seconds. | ||
+ | |||
+ | * To use reverse mode (server sends the trafic and client receives): | ||
+ | * On the Client side: '' | ||
+ | |||
+ | * To send multiple flows: | ||
+ | * On the Client side: '' | ||
+ | |||
+ | Here we are sending 2 flows in for one minute (60 seconds). Note that we need to extend more the tx time in order to have similar throughput for the 2 flows so that we don't consider it as a fairness issue. | ||
+ | |||
+ | Let's analyze flent application: | ||
+ | * On the Server side: netserver & | ||
+ | -To visualize one TCP stream: | ||
+ | * On the Client side: flent tcp_upload -p totals -l 60 -H 192.168.200.192 -t title2 -o test2.png | ||
+ | -To visualize 12 TCP streams: | ||
+ | * On the Client side: flent tcp_12up -p totals -l 60 -H 192.168.200.192 -t title3 -o test3.png | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
qos_project.txt · Last modified: 2021/08/28 09:58 by samer