Wfq
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 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 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 set traffic control QDISC type wfq default-class 8
Step 2: Set the following configuration in DUT1:
set interfaces ethernet eth0 address 10.0.0.1/24
Step 3: Ping IP address 10.0.0.1 from DUT0:
admin@DUT0$ ping 10.0.0.1 count 1 size 56 timeout 1Show 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.447 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.447/0.447/0.447/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 8080Expect this output in
DUT0:Connecting to host 10.0.0.1, port 8080 [ 5] local 10.0.0.2 port 42808 connected to 10.0.0.1 port 8080 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.1 MBytes 119 Mbits/sec 0 216 KBytes [ 5] 1.00-2.00 sec 11.3 MBytes 94.9 Mbits/sec 0 225 KBytes [ 5] 2.00-3.00 sec 11.5 MBytes 96.4 Mbits/sec 16 171 KBytes [ 5] 3.00-4.00 sec 10.4 MBytes 87.0 Mbits/sec 0 206 KBytes [ 5] 4.00-5.00 sec 12.0 MBytes 101 Mbits/sec 0 206 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.3 MBytes 99.5 Mbits/sec 16 sender [ 5] 0.00-5.00 sec 58.2 MBytes 97.6 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 1234Expect this output in
DUT0:Connecting to host 10.0.0.1, port 1234 [ 5] local 10.0.0.2 port 53590 connected to 10.0.0.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.5 MBytes 122 Mbits/sec 0 301 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 93.8 Mbits/sec 0 315 KBytes [ 5] 2.00-3.00 sec 11.8 MBytes 99.1 Mbits/sec 0 328 KBytes [ 5] 3.00-4.00 sec 10.9 MBytes 91.7 Mbits/sec 0 328 KBytes [ 5] 4.00-5.00 sec 11.6 MBytes 97.5 Mbits/sec 0 328 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 60.1 MBytes 101 Mbits/sec 0 sender [ 5] 0.00-5.01 sec 58.5 MBytes 98.0 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 128167650 84702 1 1:1 QDISC class 1 1:0 63918404 42238 0 1:2 QDISC class 2 1:0 64248390 42456 0 1:8 QDISC class 8 (default) 1:0 856 8 0 2:0 - fq_codel 1:1 63918404 42238 1 3:0 - fq_codel 1:2 64248390 42456 0 4:0 - fq_codel 1:8 856 8 0