Netem

The following scenario shows how to configure a Network Emulator qdisc.

../../../../../_images/topology3.svg

Test NetEm QDisc

Description

In this scenario, a Network Emulator (NetEm) qdisc is configured in DUT0 to add certain characteristics (like delay or packet loss) to packets leaving the ‘eth0’ interface.

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 network-emulator packet-corruption 0.05
set traffic control QDISC type network-emulator network-delay 0.05
set traffic control QDISC type network-emulator packet-loss 0.05

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 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.818 ms

--- 10.0.0.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.818/0.818/0.818/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
Expect this output in DUT0:
Connecting to host 10.0.0.1, port 8080
[  5] local 10.0.0.2 port 49216 connected to 10.0.0.1 port 8080
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   298 MBytes  2.50 Gbits/sec   48    461 KBytes
[  5]   1.00-2.00   sec   246 MBytes  2.06 Gbits/sec   45    522 KBytes
[  5]   2.00-3.00   sec   238 MBytes  2.00 Gbits/sec   92    438 KBytes
[  5]   3.00-4.00   sec   246 MBytes  2.06 Gbits/sec   48    457 KBytes
[  5]   4.00-5.01   sec   264 MBytes  2.20 Gbits/sec   95    267 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.01   sec  1.26 GBytes  2.16 Gbits/sec  328             sender
[  5]   0.00-5.01   sec  1.26 GBytes  2.16 Gbits/sec                  receiver

iperf Done.

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

netem
Show output
Traffic control for interface 'eth0' - 'egress' mode

------------------------------------------------------------------------
ID   traffic control  type   parent  bytes sent  pkts sent  pkts dropped
------------------------------------------------------------------------
1:0  QDISC            netem  root    1414792964     935850             8