Wfq

Contents

The following scenario shows how to configure a WFQ qdisc.

Test WFQ QDisc

Description

In this scenario, a WFQ qdisc is configured in DUT0 (‘eth0’ interface) to achieve linksharing among a hierarchy of classes. Since hardware offload is not configured, HTB is used internally.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces ethernet eth0 address 10.0.0.2/24
set interfaces ethernet eth0 traffic control out QDISC
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set traffic control QDISC type wfq bandwidth 100
set traffic control QDISC type wfq class 1 weight 50
set traffic control QDISC type wfq class 2 weight 30
set traffic control QDISC type wfq class 8 weight 20
set traffic control QDISC type wfq default-class 8
set traffic control QDISC type wfq match 1 class 1
set traffic control QDISC type wfq match 1 ip destination port 8080
set traffic control QDISC type wfq match 2 class 2
set traffic control QDISC type wfq match 2 ip protocol tcp

Step 2: Set the following configuration in DUT1 :

set interfaces ethernet eth0 address 10.0.0.1/24
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 3: Ping IP address 10.0.0.1 from DUT0:

admin@DUT0$ ping 10.0.0.1 count 1 size 56 timeout 1

Show output

PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.532 ms

--- 10.0.0.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.532/0.532/0.532/0.000 ms

Step 4: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 8080
admin@DUT0$ monitor test performance client 10.0.0.1 duration 5 port 8080 parallel 1

Expect this output in DUT0:

Connecting to host 10.0.0.1, port 8080
[  5] local 10.0.0.2 port 59818 connected to 10.0.0.1 port 8080
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  13.9 MBytes   117 Mbits/sec   99    127 KBytes
[  5]   1.00-2.00   sec  11.4 MBytes  95.9 Mbits/sec   46    113 KBytes
[  5]   2.00-3.00   sec  11.2 MBytes  94.4 Mbits/sec   56   97.6 KBytes
[  5]   3.00-4.00   sec  11.5 MBytes  96.4 Mbits/sec   12    126 KBytes
[  5]   4.00-5.00   sec  11.5 MBytes  96.4 Mbits/sec   32    102 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.6 MBytes  99.9 Mbits/sec  245             sender
[  5]   0.00-5.00   sec  58.4 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

Step 5: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 1234
admin@DUT0$ monitor test performance client 10.0.0.1 duration 5 port 1234 parallel 1

Expect this output in DUT0:

Connecting to host 10.0.0.1, port 1234
[  5] local 10.0.0.2 port 58644 connected to 10.0.0.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  16.2 MBytes   136 Mbits/sec  209   90.5 KBytes
[  5]   1.00-2.00   sec  10.7 MBytes  89.4 Mbits/sec    9    124 KBytes
[  5]   2.00-3.00   sec  11.8 MBytes  98.6 Mbits/sec   30    119 KBytes
[  5]   3.00-4.00   sec  11.8 MBytes  99.2 Mbits/sec   15    102 KBytes
[  5]   4.00-5.00   sec  10.7 MBytes  89.5 Mbits/sec   15    129 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  61.1 MBytes   103 Mbits/sec  278             sender
[  5]   0.00-5.01   sec  58.4 MBytes  97.9 Mbits/sec                  receiver

iperf Done.

Step 6: Run command traffic control show at DUT0 and check if output contains the following tokens:

htb
class 1
class 2
class 8 (default)

Show output

Traffic control for interface 'eth0' - 'egress' mode

------------------------------------------------------------------------------------
ID   traffic control        type         parent  bytes sent  pkts sent  pkts dropped
------------------------------------------------------------------------------------
1:0  QDISC            htb                root     128262804      84760            22
1:1  QDISC            class 1            1:0       64146917      42387             0
1:2  QDISC            class 2            1:0       64115117      42366             0
1:8  QDISC            class 8 (default)  1:0            770          7             0
2:0  -                fq_codel           1:1       64146917      42387            10
3:0  -                fq_codel           1:2       64115117      42366            12
4:0  -                fq_codel           1:8            770          7             0

Note

Adding the ['set traffic control QDISC type wfq hardware-offload'] command in DUT0, hardware offload is enabled in the WFQ qdisc. In this case, CEETM is used internally.

---