Tc Snmp Monitor

These scenarios show how to configure a traffic control discipline in different interfaces to monitor its statistics using SNMP protocol.

Test Traffic Control OIDs On Ethernet Interface

Description

In this scenario, traffic control disciplines are attached to an Ethernet interface.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces ethernet eth0 address 192.168.100.1/24
set interfaces ethernet eth0 traffic control in NETEM
set interfaces ethernet eth0 traffic control out WFQ
set service snmp community COMMUNITY2TEST
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set traffic control NETEM type network-emulator packet-loss 0.5
set traffic control WFQ type wfq bandwidth 100
set traffic control WFQ type wfq class 1 weight 10
set traffic control WFQ type wfq class 2 weight 10
set traffic control WFQ type wfq default-class 2
set traffic control WFQ type wfq match 1 class 1
set traffic control WFQ type wfq match 1 ip protocol tcp
set traffic control WFQ type wfq match 1 ip source port 1234

Step 2: Set the following configuration in DUT1 :

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

Step 3: Ping IP address 192.168.100.1 from DUT1:

admin@DUT1$ ping 192.168.100.1 count 1 size 56 timeout 1
Show output
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.387 ms

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

Step 4: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 1234
admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 1234 parallel 1
Expect this output in DUT1:
Connecting to host 192.168.100.1, port 1234
[  5] local 192.168.100.2 port 53098 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  84.6 MBytes   710 Mbits/sec  311   36.8 KBytes
[  5]   1.00-2.00   sec  89.4 MBytes   750 Mbits/sec  301   41.0 KBytes
[  5]   2.00-3.00   sec  96.3 MBytes   808 Mbits/sec  339   26.9 KBytes
[  5]   3.00-4.00   sec   118 MBytes   992 Mbits/sec  432   24.0 KBytes
[  5]   4.00-5.00   sec   178 MBytes  1.49 Gbits/sec  670   41.0 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   567 MBytes   951 Mbits/sec  2053             sender
[  5]   0.00-5.00   sec   566 MBytes   950 Mbits/sec                  receiver

iperf Done.

Step 5: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 4321
admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 4321 parallel 1
Expect this output in DUT1:
Connecting to host 192.168.100.1, port 4321
[  5] local 192.168.100.2 port 45836 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   184 MBytes  1.55 Gbits/sec  710   33.9 KBytes
[  5]   1.00-2.00   sec   215 MBytes  1.80 Gbits/sec  773   39.6 KBytes
[  5]   2.00-3.00   sec   218 MBytes  1.83 Gbits/sec  743   52.3 KBytes
[  5]   3.00-4.00   sec   204 MBytes  1.71 Gbits/sec  774   56.6 KBytes
[  5]   4.00-5.00   sec   190 MBytes  1.60 Gbits/sec  630   24.0 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1011 MBytes  1.70 Gbits/sec  3630             sender
[  5]   0.00-5.00   sec  1009 MBytes  1.69 Gbits/sec                  receiver

iperf Done.

Step 6: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 1234
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 1234 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 1234
[  5] local 192.168.100.1 port 45378 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.1 MBytes   118 Mbits/sec  142    109 KBytes
[  5]   1.00-2.00   sec  11.8 MBytes  99.0 Mbits/sec    9    102 KBytes
[  5]   2.00-3.00   sec  11.2 MBytes  93.8 Mbits/sec    6    132 KBytes
[  5]   3.00-4.00   sec  11.2 MBytes  93.8 Mbits/sec   21   91.9 KBytes
[  5]   4.00-5.00   sec  11.8 MBytes  99.0 Mbits/sec   14   87.7 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  60.1 MBytes   101 Mbits/sec  192             sender
[  5]   0.00-5.00   sec  58.5 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

Step 7: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 4321
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 4321 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 4321
[  5] local 192.168.100.1 port 48488 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  13.8 MBytes   116 Mbits/sec   56    103 KBytes
[  5]   1.00-2.00   sec  11.7 MBytes  98.5 Mbits/sec    7   97.6 KBytes
[  5]   2.00-3.00   sec  11.2 MBytes  93.8 Mbits/sec   11   89.1 KBytes
[  5]   3.00-4.00   sec  11.7 MBytes  98.5 Mbits/sec   10   86.3 KBytes
[  5]   4.00-5.00   sec  11.2 MBytes  94.4 Mbits/sec    7    117 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.7 MBytes   100 Mbits/sec   91             sender
[  5]   0.00-5.00   sec  58.4 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

Step 8: Run command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl at DUT0 and check if output matches the following regular expressions:

OutKind\.[^=]+ = STRING: (htb|ceetm)
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: \d+
OutRate\.[^=]+ = INTEGER: 100000000
InPps\.[^=]+ = INTEGER: [1-9]\d*
InDrops\.[^=]+ = INTEGER: [1-9]\d*
InOverlimits\.[^=]+ = INTEGER: \d+
InRate\.[^=]+ = INTEGER: 0
OutClassPackets\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassPackets\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassDrops\.[^=]+\.1 = INTEGER: \d+
OutClassDrops\.[^=]+\.2 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.1 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.2 = INTEGER: \d+
OutPps\.[^=]+ = INTEGER: [1-9]\d*
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutPackets."eth0" = INTEGER: 435333
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutPps."eth0" = INTEGER: 13082
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBytes."eth0" = INTEGER: 151659393
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutDrops."eth0" = INTEGER: 23
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutKind."eth0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBps."eth0" = INTEGER: 9393039
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutOverlimits."eth0" = INTEGER: 7625
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutRate."eth0" = INTEGER: 100000000
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassTag."eth0".1 = INTEGER: 1
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassTag."eth0".2 = INTEGER: 2
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassPackets."eth0".1 = INTEGER: 138309
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassPackets."eth0".2 = INTEGER: 297024
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".1 = INTEGER: 9208668
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".2 = INTEGER: 142450725
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassDrops."eth0".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassDrops."eth0".2 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassOverlimits."eth0".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassOverlimits."eth0".2 = INTEGER: 4098
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPackets."eth0" = INTEGER: 1153885
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPps."eth0" = INTEGER: 25121
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBytes."eth0" = INTEGER: 1727381637
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInDrops."eth0" = INTEGER: 5733
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInKind."eth0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBps."eth0" = INTEGER: 36778578
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInOverlimits."eth0" = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInRate."eth0" = INTEGER: 0

Test Traffic Control OIDs On Ethernet VIF-S Interface

Description

In this scenario, traffic control disciplines are attached to a VLAN-aware Ethernet interface.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces ethernet eth0 vif 100 address 192.168.100.1/24
set interfaces ethernet eth0 vif 100 traffic control in NETEM
set interfaces ethernet eth0 vif 100 traffic control out WFQ
set service snmp community COMMUNITY2TEST
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set traffic control NETEM type network-emulator packet-loss 0.5
set traffic control WFQ type wfq bandwidth 100
set traffic control WFQ type wfq class 1 weight 10
set traffic control WFQ type wfq class 2 weight 10
set traffic control WFQ type wfq default-class 2
set traffic control WFQ type wfq match 1 class 1
set traffic control WFQ type wfq match 1 ip protocol tcp
set traffic control WFQ type wfq match 1 ip source port 1234

Step 2: Set the following configuration in DUT1 :

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

Step 3: Ping IP address 192.168.100.1 from DUT1:

admin@DUT1$ ping 192.168.100.1 count 1 size 56 timeout 1
Show output
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.303 ms

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

Step 4: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 1234
admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 1234 parallel 1
Expect this output in DUT1:
Connecting to host 192.168.100.1, port 1234
[  5] local 192.168.100.2 port 33776 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   103 MBytes   862 Mbits/sec  329   9.90 KBytes
[  5]   1.00-2.00   sec   162 MBytes  1.36 Gbits/sec  573   29.7 KBytes
[  5]   2.00-3.00   sec   226 MBytes  1.90 Gbits/sec  830   22.6 KBytes
[  5]   3.00-4.00   sec   216 MBytes  1.81 Gbits/sec  754   36.8 KBytes
[  5]   4.00-5.00   sec   241 MBytes  2.02 Gbits/sec  856   26.9 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   948 MBytes  1.59 Gbits/sec  3342             sender
[  5]   0.00-5.00   sec   947 MBytes  1.59 Gbits/sec                  receiver

iperf Done.

Step 5: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 4321
admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 4321 parallel 1
Expect this output in DUT1:
Connecting to host 192.168.100.1, port 4321
[  5] local 192.168.100.2 port 38476 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   224 MBytes  1.88 Gbits/sec  780   22.6 KBytes
[  5]   1.00-2.00   sec   233 MBytes  1.96 Gbits/sec  797   31.1 KBytes
[  5]   2.00-3.00   sec   234 MBytes  1.96 Gbits/sec  859   25.5 KBytes
[  5]   3.00-4.00   sec   212 MBytes  1.78 Gbits/sec  806   52.3 KBytes
[  5]   4.00-5.00   sec   205 MBytes  1.72 Gbits/sec  705   25.5 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.08 GBytes  1.86 Gbits/sec  3947             sender
[  5]   0.00-5.01   sec  1.08 GBytes  1.86 Gbits/sec                  receiver

iperf Done.

Step 6: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 1234
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 1234 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 1234
[  5] local 192.168.100.1 port 57532 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.0 MBytes   117 Mbits/sec   97    107 KBytes
[  5]   1.00-2.00   sec  11.2 MBytes  94.4 Mbits/sec   20    134 KBytes
[  5]   2.00-3.00   sec  11.3 MBytes  94.9 Mbits/sec   20    122 KBytes
[  5]   3.00-4.00   sec  11.4 MBytes  95.9 Mbits/sec   31    106 KBytes
[  5]   4.00-5.00   sec  11.6 MBytes  97.5 Mbits/sec    5    102 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.6 MBytes   100 Mbits/sec  173             sender
[  5]   0.00-5.00   sec  58.4 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

Step 7: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 4321
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 4321 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 4321
[  5] local 192.168.100.1 port 55574 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  13.7 MBytes   115 Mbits/sec   76    100 KBytes
[  5]   1.00-2.00   sec  11.5 MBytes  96.4 Mbits/sec    3    134 KBytes
[  5]   2.00-3.00   sec  11.5 MBytes  96.4 Mbits/sec   47    124 KBytes
[  5]   3.00-4.00   sec  11.4 MBytes  95.4 Mbits/sec   20    112 KBytes
[  5]   4.00-5.00   sec  11.2 MBytes  94.3 Mbits/sec   50   97.6 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.3 MBytes  99.5 Mbits/sec  196             sender
[  5]   0.00-5.00   sec  58.5 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

Step 8: Run command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl at DUT0 and check if output matches the following regular expressions:

OutKind\.[^=]+ = STRING: (htb|ceetm)
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: \d+
OutRate\.[^=]+ = INTEGER: 100000000
InPps\.[^=]+ = INTEGER: [1-9]\d*
InDrops\.[^=]+ = INTEGER: [1-9]\d*
InOverlimits\.[^=]+ = INTEGER: \d+
InRate\.[^=]+ = INTEGER: 0
OutClassPackets\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassPackets\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassDrops\.[^=]+\.1 = INTEGER: \d+
OutClassDrops\.[^=]+\.2 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.1 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.2 = INTEGER: \d+
OutPps\.[^=]+ = INTEGER: [1-9]\d*
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutPackets."eth0"."100" = INTEGER: 319786
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutPps."eth0"."100" = INTEGER: 10119
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBytes."eth0"."100" = INTEGER: 144141836
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutDrops."eth0"."100" = INTEGER: 20
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutKind."eth0"."100" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBps."eth0"."100" = INTEGER: 9383417
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutOverlimits."eth0"."100" = INTEGER: 7242
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutRate."eth0"."100" = INTEGER: 100000000
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassTag."eth0"."100".1 = INTEGER: 1
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassTag."eth0"."100".2 = INTEGER: 2
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassPackets."eth0"."100".1 = INTEGER: 116866
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassPackets."eth0"."100".2 = INTEGER: 202920
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".1 = INTEGER: 7835033
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".2 = INTEGER: 136306803
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassDrops."eth0"."100".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassDrops."eth0"."100".2 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassOverlimits."eth0"."100".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassOverlimits."eth0"."100".2 = INTEGER: 3895
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPackets."eth0"."100" = INTEGER: 1500040
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPps."eth0"."100" = INTEGER: 28355
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBytes."eth0"."100" = INTEGER: 2254307789
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInDrops."eth0"."100" = INTEGER: 7340
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInKind."eth0"."100" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBps."eth0"."100" = INTEGER: 41798697
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInOverlimits."eth0"."100" = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInRate."eth0"."100" = INTEGER: 0

Test Traffic Control OIDs On Bridge Interface

Description

In this scenario, traffic control disciplines are attached to a Bridge interface.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces bridge br0 address 192.168.100.1/24
set interfaces bridge br0 traffic control in NETEM
set interfaces bridge br0 traffic control out WFQ
set interfaces ethernet eth0 bridge-group bridge br0
set service snmp community COMMUNITY2TEST
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set traffic control NETEM type network-emulator packet-loss 0.5
set traffic control WFQ type wfq bandwidth 100
set traffic control WFQ type wfq class 1 weight 10
set traffic control WFQ type wfq class 2 weight 10
set traffic control WFQ type wfq default-class 2
set traffic control WFQ type wfq match 1 class 1
set traffic control WFQ type wfq match 1 ip protocol tcp
set traffic control WFQ type wfq match 1 ip source port 1234

Step 2: Set the following configuration in DUT1 :

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

Step 3: Ping IP address 192.168.100.1 from DUT1:

admin@DUT1$ ping 192.168.100.1 count 1 size 56 timeout 1
Show output
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.272 ms

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

Step 4: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 1234
admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 1234 parallel 1
Expect this output in DUT1:
Connecting to host 192.168.100.1, port 1234
[  5] local 192.168.100.2 port 37108 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   106 MBytes   890 Mbits/sec  352   26.9 KBytes
[  5]   1.00-2.00   sec  77.0 MBytes   645 Mbits/sec  303   41.0 KBytes
[  5]   2.00-3.00   sec   178 MBytes  1.49 Gbits/sec  623   45.2 KBytes
[  5]   3.00-4.00   sec   193 MBytes  1.62 Gbits/sec  719   35.4 KBytes
[  5]   4.00-5.00   sec   192 MBytes  1.61 Gbits/sec  698   21.2 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   746 MBytes  1.25 Gbits/sec  2695             sender
[  5]   0.00-5.00   sec   745 MBytes  1.25 Gbits/sec                  receiver

iperf Done.

Step 5: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 4321
admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 4321 parallel 1
Expect this output in DUT1:
Connecting to host 192.168.100.1, port 4321
[  5] local 192.168.100.2 port 57684 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   204 MBytes  1.71 Gbits/sec  750   59.4 KBytes
[  5]   1.00-2.00   sec   216 MBytes  1.81 Gbits/sec  804   42.4 KBytes
[  5]   2.00-3.00   sec   231 MBytes  1.94 Gbits/sec  811   24.0 KBytes
[  5]   3.00-4.00   sec   220 MBytes  1.85 Gbits/sec  822   26.9 KBytes
[  5]   4.00-5.00   sec   223 MBytes  1.87 Gbits/sec  802   36.8 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.07 GBytes  1.84 Gbits/sec  3989             sender
[  5]   0.00-5.00   sec  1.07 GBytes  1.83 Gbits/sec                  receiver

iperf Done.

Step 6: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 1234
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 1234 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 1234
[  5] local 192.168.100.1 port 46956 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.2 MBytes   119 Mbits/sec  165    105 KBytes
[  5]   1.00-2.00   sec  11.8 MBytes  99.0 Mbits/sec   10    134 KBytes
[  5]   2.00-3.00   sec  11.2 MBytes  93.8 Mbits/sec   18    119 KBytes
[  5]   3.00-4.00   sec  11.2 MBytes  93.8 Mbits/sec    6    112 KBytes
[  5]   4.00-5.00   sec  11.8 MBytes  99.0 Mbits/sec   10   96.2 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  60.1 MBytes   101 Mbits/sec  209             sender
[  5]   0.00-5.00   sec  58.4 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

Step 7: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 4321
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 4321 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 4321
[  5] local 192.168.100.1 port 49242 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.2 MBytes   119 Mbits/sec   96    137 KBytes
[  5]   1.00-2.00   sec  11.2 MBytes  93.8 Mbits/sec   36    120 KBytes
[  5]   2.00-3.00   sec  11.7 MBytes  98.5 Mbits/sec   17    146 KBytes
[  5]   3.00-4.00   sec  11.3 MBytes  94.9 Mbits/sec   43    115 KBytes
[  5]   4.00-5.00   sec  11.2 MBytes  93.8 Mbits/sec   10    109 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.6 MBytes   100 Mbits/sec  202             sender
[  5]   0.00-5.00   sec  58.4 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

Step 8: Run command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl at DUT0 and check if output matches the following regular expressions:

OutKind\.[^=]+ = STRING: (htb|ceetm)
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: \d+
OutRate\.[^=]+ = INTEGER: 100000000
InPps\.[^=]+ = INTEGER: [1-9]\d*
InDrops\.[^=]+ = INTEGER: [1-9]\d*
InOverlimits\.[^=]+ = INTEGER: \d+
InRate\.[^=]+ = INTEGER: 0
OutClassPackets\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassPackets\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassDrops\.[^=]+\.1 = INTEGER: \d+
OutClassDrops\.[^=]+\.2 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.1 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.2 = INTEGER: \d+
OutPps\.[^=]+ = INTEGER: [1-9]\d*
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutPackets."br0" = INTEGER: 353826
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutPps."br0" = INTEGER: 9822
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBytes."br0" = INTEGER: 146322308
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutDrops."br0" = INTEGER: 21
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutKind."br0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBps."br0" = INTEGER: 9375983
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutOverlimits."br0" = INTEGER: 7194
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutRate."br0" = INTEGER: 100000000
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassTag."br0".1 = INTEGER: 1
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassTag."br0".2 = INTEGER: 2
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassPackets."br0".1 = INTEGER: 172513
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassPackets."br0".2 = INTEGER: 181313
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".1 = INTEGER: 11486683
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".2 = INTEGER: 134835625
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassDrops."br0".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassDrops."br0".2 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassOverlimits."br0".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassOverlimits."br0".2 = INTEGER: 3870
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPackets."br0" = INTEGER: 1347577
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPps."br0" = INTEGER: 23899
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBytes."br0" = INTEGER: 2017450300
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInDrops."br0" = INTEGER: 6755
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInKind."br0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBps."br0" = INTEGER: 34677021
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInOverlimits."br0" = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInRate."br0" = INTEGER: 0

Test Traffic Control OIDs On Bridge VIF-S Interface

Description

In this scenario, traffic control disciplines are attached to a VLAN-aware bridge interface.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces bridge br0 vif 100 address 192.168.100.1/24
set interfaces bridge br0 vif 100 traffic control in NETEM
set interfaces bridge br0 vif 100 traffic control out WFQ
set interfaces bridge br0 vlan 100
set interfaces ethernet eth0 bridge-group bridge br0
set interfaces ethernet eth0 bridge-group vlan 100
set service snmp community COMMUNITY2TEST
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set traffic control NETEM type network-emulator packet-loss 0.5
set traffic control WFQ type wfq bandwidth 100
set traffic control WFQ type wfq class 1 weight 10
set traffic control WFQ type wfq class 2 weight 10
set traffic control WFQ type wfq default-class 2
set traffic control WFQ type wfq match 1 class 1
set traffic control WFQ type wfq match 1 ip protocol tcp
set traffic control WFQ type wfq match 1 ip source port 1234

Step 2: Set the following configuration in DUT1 :

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

Step 3: Ping IP address 192.168.100.1 from DUT1:

admin@DUT1$ ping 192.168.100.1 count 1 size 56 timeout 1
Show output
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.288 ms

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

Step 4: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 1234
admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 1234 parallel 1
Expect this output in DUT1:
Connecting to host 192.168.100.1, port 1234
[  5] local 192.168.100.2 port 57272 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  96.5 MBytes   810 Mbits/sec  325   32.5 KBytes
[  5]   1.00-2.00   sec   191 MBytes  1.60 Gbits/sec  691   19.8 KBytes
[  5]   2.00-3.00   sec   195 MBytes  1.64 Gbits/sec  710   49.5 KBytes
[  5]   3.00-4.00   sec   180 MBytes  1.51 Gbits/sec  677   31.1 KBytes
[  5]   4.00-5.00   sec   189 MBytes  1.58 Gbits/sec  730   32.5 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   852 MBytes  1.43 Gbits/sec  3133             sender
[  5]   0.00-5.00   sec   851 MBytes  1.43 Gbits/sec                  receiver

iperf Done.

Step 5: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 4321
admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 4321 parallel 1
Expect this output in DUT1:
Connecting to host 192.168.100.1, port 4321
[  5] local 192.168.100.2 port 57280 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   194 MBytes  1.63 Gbits/sec  644   33.9 KBytes
[  5]   1.00-2.00   sec   198 MBytes  1.66 Gbits/sec  750   65.0 KBytes
[  5]   2.00-3.00   sec   193 MBytes  1.62 Gbits/sec  686   43.8 KBytes
[  5]   3.00-4.00   sec   191 MBytes  1.60 Gbits/sec  699   29.7 KBytes
[  5]   4.00-5.00   sec   194 MBytes  1.62 Gbits/sec  727   35.4 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   969 MBytes  1.63 Gbits/sec  3506             sender
[  5]   0.00-5.00   sec   968 MBytes  1.62 Gbits/sec                  receiver

iperf Done.

Step 6: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 1234
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 1234 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 1234
[  5] local 192.168.100.1 port 35352 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.1 MBytes   118 Mbits/sec   92    116 KBytes
[  5]   1.00-2.00   sec  11.1 MBytes  92.8 Mbits/sec   16   97.6 KBytes
[  5]   2.00-3.00   sec  11.3 MBytes  94.9 Mbits/sec    7    129 KBytes
[  5]   3.00-4.00   sec  11.5 MBytes  96.4 Mbits/sec   15    124 KBytes
[  5]   4.00-5.00   sec  11.4 MBytes  95.4 Mbits/sec   31    117 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.4 MBytes  99.6 Mbits/sec  161             sender
[  5]   0.00-5.00   sec  58.4 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

Step 7: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 4321
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 4321 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 4321
[  5] local 192.168.100.1 port 40884 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.4 MBytes   121 Mbits/sec  109    110 KBytes
[  5]   1.00-2.00   sec  11.2 MBytes  94.4 Mbits/sec   12    136 KBytes
[  5]   2.00-3.00   sec  11.2 MBytes  94.4 Mbits/sec   59    132 KBytes
[  5]   3.00-4.00   sec  11.8 MBytes  99.0 Mbits/sec   47    113 KBytes
[  5]   4.00-5.00   sec  11.2 MBytes  93.8 Mbits/sec   73    100 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.9 MBytes   100 Mbits/sec  300             sender
[  5]   0.00-5.00   sec  58.4 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

Step 8: Run command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl at DUT0 and check if output matches the following regular expressions:

OutKind\.[^=]+ = STRING: (htb|ceetm)
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: \d+
OutRate\.[^=]+ = INTEGER: 100000000
InPps\.[^=]+ = INTEGER: [1-9]\d*
InDrops\.[^=]+ = INTEGER: [1-9]\d*
InOverlimits\.[^=]+ = INTEGER: \d+
InRate\.[^=]+ = INTEGER: 0
OutClassPackets\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassPackets\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassDrops\.[^=]+\.1 = INTEGER: \d+
OutClassDrops\.[^=]+\.2 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.1 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.2 = INTEGER: \d+
OutPps\.[^=]+ = INTEGER: [1-9]\d*
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutPackets."br0"."100" = INTEGER: 485013
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutPps."br0"."100" = INTEGER: 13388
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBytes."br0"."100" = INTEGER: 155004649
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutDrops."br0"."100" = INTEGER: 21
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutKind."br0"."100" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBps."br0"."100" = INTEGER: 9509268
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutOverlimits."br0"."100" = INTEGER: 7323
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutRate."br0"."100" = INTEGER: 100000000
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassTag."br0"."100".1 = INTEGER: 1
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassTag."br0"."100".2 = INTEGER: 2
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassPackets."br0"."100".1 = INTEGER: 198120
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassPackets."br0"."100".2 = INTEGER: 286893
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".1 = INTEGER: 13187930
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".2 = INTEGER: 141816719
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassDrops."br0"."100".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassDrops."br0"."100".2 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassOverlimits."br0"."100".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassOverlimits."br0"."100".2 = INTEGER: 3944
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPackets."br0"."100" = INTEGER: 1332573
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPps."br0"."100" = INTEGER: 26495
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBytes."br0"."100" = INTEGER: 1995921522
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInDrops."br0"."100" = INTEGER: 6716
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInKind."br0"."100" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBps."br0"."100" = INTEGER: 38578425
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInOverlimits."br0"."100" = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInRate."br0"."100" = INTEGER: 0

Test Traffic Control OIDs On Bonding Interface

Description

In this scenario, traffic control disciplines are attached to a Bonding interface.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces bonding bond0 address 192.168.100.1/24
set interfaces bonding bond0 miimon 1
set interfaces bonding bond0 traffic control in NETEM
set interfaces bonding bond0 traffic control out WFQ
set interfaces ethernet eth0 bond-group bond0
set interfaces ethernet eth1 bond-group bond0
set service snmp community COMMUNITY2TEST
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set traffic control NETEM type network-emulator packet-loss 0.5
set traffic control WFQ type wfq bandwidth 100
set traffic control WFQ type wfq class 1 weight 10
set traffic control WFQ type wfq class 2 weight 10
set traffic control WFQ type wfq default-class 2
set traffic control WFQ type wfq match 1 class 1
set traffic control WFQ type wfq match 1 ip protocol tcp
set traffic control WFQ type wfq match 1 ip source port 1234

Step 2: Set the following configuration in DUT1 :

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

Step 3: Ping IP address 192.168.100.1 from DUT1:

admin@DUT1$ ping 192.168.100.1 count 1 size 56 timeout 1
Show output
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.302 ms

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

Step 4: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 1234
admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 1234 parallel 1
Expect this output in DUT1:
Connecting to host 192.168.100.1, port 1234
[  5] local 192.168.100.2 port 36596 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   101 MBytes   850 Mbits/sec  338   32.5 KBytes
[  5]   1.00-2.00   sec   100 MBytes   839 Mbits/sec  318   43.8 KBytes
[  5]   2.00-3.00   sec   185 MBytes  1.55 Gbits/sec  674   35.4 KBytes
[  5]   3.00-4.00   sec   218 MBytes  1.83 Gbits/sec  803   24.0 KBytes
[  5]   4.00-5.00   sec   212 MBytes  1.77 Gbits/sec  789   35.4 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   816 MBytes  1.37 Gbits/sec  2922             sender
[  5]   0.00-5.00   sec   816 MBytes  1.37 Gbits/sec                  receiver

iperf Done.

Step 5: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 4321
admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 4321 parallel 1
Expect this output in DUT1:
Connecting to host 192.168.100.1, port 4321
[  5] local 192.168.100.2 port 40564 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   192 MBytes  1.61 Gbits/sec  707   55.1 KBytes
[  5]   1.00-2.00   sec   186 MBytes  1.56 Gbits/sec  694   38.2 KBytes
[  5]   2.00-3.00   sec   183 MBytes  1.54 Gbits/sec  669   35.4 KBytes
[  5]   3.00-4.00   sec   199 MBytes  1.67 Gbits/sec  715   25.5 KBytes
[  5]   4.00-5.00   sec   208 MBytes  1.75 Gbits/sec  751   31.1 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   969 MBytes  1.63 Gbits/sec  3536             sender
[  5]   0.00-5.00   sec   969 MBytes  1.62 Gbits/sec                  receiver

iperf Done.

Step 6: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 1234
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 1234 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 1234
[  5] local 192.168.100.1 port 48552 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.4 MBytes   121 Mbits/sec   91    127 KBytes
[  5]   1.00-2.00   sec  11.2 MBytes  94.4 Mbits/sec   70    113 KBytes
[  5]   2.00-3.00   sec  11.2 MBytes  93.8 Mbits/sec   20    100 KBytes
[  5]   3.00-4.00   sec  11.8 MBytes  99.0 Mbits/sec   11    129 KBytes
[  5]   4.00-5.00   sec  11.2 MBytes  94.4 Mbits/sec   22    126 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.9 MBytes   100 Mbits/sec  214             sender
[  5]   0.00-5.00   sec  58.4 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

Step 7: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 4321
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 4321 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 4321
[  5] local 192.168.100.1 port 43402 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.0 MBytes   117 Mbits/sec   71   82.0 KBytes
[  5]   1.00-2.00   sec  11.3 MBytes  94.9 Mbits/sec   11   83.4 KBytes
[  5]   2.00-3.00   sec  11.4 MBytes  95.4 Mbits/sec    1    110 KBytes
[  5]   3.00-4.00   sec  11.3 MBytes  94.9 Mbits/sec    4    112 KBytes
[  5]   4.00-5.00   sec  11.4 MBytes  95.4 Mbits/sec   37    103 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.4 MBytes  99.6 Mbits/sec  124             sender
[  5]   0.00-5.00   sec  58.4 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

Step 8: Run command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl at DUT0 and check if output matches the following regular expressions:

OutKind\.[^=]+ = STRING: (htb|ceetm)
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: \d+
OutRate\.[^=]+ = INTEGER: 100000000
InPps\.[^=]+ = INTEGER: [1-9]\d*
InDrops\.[^=]+ = INTEGER: [1-9]\d*
InOverlimits\.[^=]+ = INTEGER: \d+
InRate\.[^=]+ = INTEGER: 0
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPackets."bond0" = INTEGER: 370089
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPps."bond0" = INTEGER: 11679
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBytes."bond0" = INTEGER: 147399847
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutDrops."bond0" = INTEGER: 20
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutKind."bond0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBps."bond0" = INTEGER: 9291790
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutOverlimits."bond0" = INTEGER: 7746
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutRate."bond0" = INTEGER: 100000000
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassTag."bond0".1 = INTEGER: 1
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassTag."bond0".2 = INTEGER: 2
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassPackets."bond0".1 = INTEGER: 96228
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassPackets."bond0".2 = INTEGER: 273861
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".1 = INTEGER: 6460858
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".2 = INTEGER: 140938989
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassDrops."bond0".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassDrops."bond0".2 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassOverlimits."bond0".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassOverlimits."bond0".2 = INTEGER: 4152
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPackets."bond0" = INTEGER: 1306080
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPps."bond0" = INTEGER: 27141
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBytes."bond0" = INTEGER: 1957010244
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInDrops."bond0" = INTEGER: 6525
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInKind."bond0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBps."bond0" = INTEGER: 39748087
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInOverlimits."bond0" = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInRate."bond0" = INTEGER: 0

Test Traffic Control OIDs On Tunnel Interface

Description

In this scenario, traffic control disciplines are attached to a Tunnel interface.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces ethernet eth0 address 192.168.100.1/24
set interfaces tunnel tun0 address 10.0.0.1/24
set interfaces tunnel tun0 encapsulation gre
set interfaces tunnel tun0 local-address 192.168.100.1
set interfaces tunnel tun0 remote-address 192.168.100.2
set interfaces tunnel tun0 traffic control in NETEM
set interfaces tunnel tun0 traffic control out WFQ
set service snmp community COMMUNITY2TEST
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set traffic control NETEM type network-emulator packet-loss 0.5
set traffic control WFQ type wfq bandwidth 100
set traffic control WFQ type wfq class 1 weight 10
set traffic control WFQ type wfq class 2 weight 10
set traffic control WFQ type wfq default-class 2
set traffic control WFQ type wfq match 1 class 1
set traffic control WFQ type wfq match 1 ip protocol tcp
set traffic control WFQ type wfq match 1 ip source port 1234

Step 2: Set the following configuration in DUT1 :

set interfaces ethernet eth0 address 192.168.100.2/24
set interfaces tunnel tun0 address 10.0.0.2/24
set interfaces tunnel tun0 encapsulation gre
set interfaces tunnel tun0 local-address 192.168.100.2
set interfaces tunnel tun0 remote-address 192.168.100.1
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 3: Ping IP address 10.0.0.1 from DUT1:

admin@DUT1$ 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.422 ms

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

Step 4: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 1234
admin@DUT1$ monitor test performance client 10.0.0.1 duration 5 port 1234 parallel 1
Expect this output in DUT1:
Connecting to host 10.0.0.1, port 1234
[  5] local 10.0.0.2 port 51618 connected to 10.0.0.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   200 MBytes  1.68 Gbits/sec  598   83.4 KBytes
[  5]   1.00-2.00   sec   283 MBytes  2.37 Gbits/sec  1080   41.7 KBytes
[  5]   2.00-3.00   sec   291 MBytes  2.44 Gbits/sec  955    111 KBytes
[  5]   3.00-4.00   sec   281 MBytes  2.36 Gbits/sec  1156   48.7 KBytes
[  5]   4.00-5.00   sec   272 MBytes  2.29 Gbits/sec  1146   37.5 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.30 GBytes  2.23 Gbits/sec  4935             sender
[  5]   0.00-5.00   sec  1.29 GBytes  2.22 Gbits/sec                  receiver

iperf Done.

Step 5: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 4321
admin@DUT1$ monitor test performance client 10.0.0.1 duration 5 port 4321 parallel 1
Expect this output in DUT1:
Connecting to host 10.0.0.1, port 4321
[  5] local 10.0.0.2 port 38150 connected to 10.0.0.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   252 MBytes  2.11 Gbits/sec  1181   69.5 KBytes
[  5]   1.00-2.00   sec   272 MBytes  2.28 Gbits/sec  915   75.1 KBytes
[  5]   2.00-3.00   sec   281 MBytes  2.36 Gbits/sec  1146   77.9 KBytes
[  5]   3.00-4.00   sec   294 MBytes  2.46 Gbits/sec  1356   79.3 KBytes
[  5]   4.00-5.00   sec   301 MBytes  2.53 Gbits/sec  1033   25.0 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.37 GBytes  2.35 Gbits/sec  5631             sender
[  5]   0.00-5.00   sec  1.36 GBytes  2.34 Gbits/sec                  receiver

iperf Done.

Step 6: 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.2 duration 5 port 1234 parallel 1
Expect this output in DUT0:
Connecting to host 10.0.0.2, port 1234
[  5] local 10.0.0.1 port 58790 connected to 10.0.0.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.0 MBytes   118 Mbits/sec   97    135 KBytes
[  5]   1.00-2.00   sec  11.6 MBytes  96.9 Mbits/sec   55    127 KBytes
[  5]   2.00-3.00   sec  11.6 MBytes  96.9 Mbits/sec   40    115 KBytes
[  5]   3.00-4.00   sec  11.6 MBytes  96.9 Mbits/sec    4    117 KBytes
[  5]   4.00-5.00   sec  11.6 MBytes  96.9 Mbits/sec   11   82.0 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  60.2 MBytes   101 Mbits/sec  207             sender
[  5]   0.00-5.00   sec  58.9 MBytes  98.9 Mbits/sec                  receiver

iperf Done.

Step 7: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 4321
admin@DUT0$ monitor test performance client 10.0.0.2 duration 5 port 4321 parallel 1
Expect this output in DUT0:
Connecting to host 10.0.0.2, port 4321
[  5] local 10.0.0.1 port 38596 connected to 10.0.0.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.4 MBytes   121 Mbits/sec  122    134 KBytes
[  5]   1.00-2.00   sec  11.0 MBytes  92.3 Mbits/sec   48    118 KBytes
[  5]   2.00-3.00   sec  11.6 MBytes  96.9 Mbits/sec   79    121 KBytes
[  5]   3.00-4.00   sec  11.6 MBytes  96.9 Mbits/sec    9   84.8 KBytes
[  5]   4.00-5.00   sec  11.7 MBytes  97.9 Mbits/sec   45    118 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  60.2 MBytes   101 Mbits/sec  303             sender
[  5]   0.00-5.00   sec  59.0 MBytes  98.9 Mbits/sec                  receiver

iperf Done.

Step 8: Run command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl at DUT0 and check if output matches the following regular expressions:

OutKind\.[^=]+ = STRING: (htb|ceetm)
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: \d+
OutRate\.[^=]+ = INTEGER: 100000000
InPps\.[^=]+ = INTEGER: [1-9]\d*
InDrops\.[^=]+ = INTEGER: [1-9]\d*
InOverlimits\.[^=]+ = INTEGER: \d+
InRate\.[^=]+ = INTEGER: 0
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutPackets."tun0" = INTEGER: 220362
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutPps."tun0" = INTEGER: 8452
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBytes."tun0" = INTEGER: 135307138
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutDrops."tun0" = INTEGER: 23
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutKind."tun0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBps."tun0" = INTEGER: 9280241
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutOverlimits."tun0" = INTEGER: 7678
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutRate."tun0" = INTEGER: 100000000
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassTag."tun0".1 = INTEGER: 1
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassTag."tun0".2 = INTEGER: 2
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassPackets."tun0".1 = INTEGER: 71419
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassPackets."tun0".2 = INTEGER: 148943
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".1 = INTEGER: 3748641
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".2 = INTEGER: 131558497
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassDrops."tun0".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassDrops."tun0".2 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassOverlimits."tun0".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassOverlimits."tun0".2 = INTEGER: 4096
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPackets."tun0" = INTEGER: 2013321
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPps."tun0" = INTEGER: 36560
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBytes."tun0" = INTEGER: 2957976994
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInDrops."tun0" = INTEGER: 1408
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInKind."tun0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBps."tun0" = INTEGER: 52986923
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInOverlimits."tun0" = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInRate."tun0" = INTEGER: 0