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 HTB
set service snmp community 'COMMUNITY2TEST!'
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set traffic control HTB type htb bandwidth 4
set traffic control HTB type htb class 1 bandwidth percentage 50
set traffic control HTB type htb class 2 bandwidth percentage 50
set traffic control HTB type htb default-class 2
set traffic control HTB type htb match 1 class 1
set traffic control HTB type htb match 1 ip protocol tcp
set traffic control HTB type htb match 1 ip source port 1234
set traffic control NETEM type network-emulator packet-loss 0.5

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

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.271/0.271/0.271/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 51564 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  12.6 MBytes   106 Mbits/sec   42   28.3 KBytes
[  5]   1.00-2.00   sec  10.9 MBytes  91.7 Mbits/sec   37   19.8 KBytes
[  5]   2.00-3.00   sec  13.0 MBytes   109 Mbits/sec   50   25.5 KBytes
[  5]   3.00-4.00   sec  12.4 MBytes   104 Mbits/sec   57   26.9 KBytes
[  5]   4.00-5.00   sec  12.4 MBytes   104 Mbits/sec   50   14.1 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  61.4 MBytes   103 Mbits/sec  236             sender
[  5]   0.00-5.00   sec  60.0 MBytes   101 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 44870 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  16.2 MBytes   136 Mbits/sec   53   53.7 KBytes
[  5]   1.00-2.00   sec  21.1 MBytes   177 Mbits/sec   73   17.0 KBytes
[  5]   2.00-3.00   sec  22.4 MBytes   188 Mbits/sec   78   43.8 KBytes
[  5]   3.00-4.00   sec  17.2 MBytes   144 Mbits/sec   73   67.9 KBytes
[  5]   4.00-5.00   sec  25.7 MBytes   216 Mbits/sec   82   17.0 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   103 MBytes   172 Mbits/sec  359             sender
[  5]   0.00-5.00   sec   102 MBytes   171 Mbits/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 39912 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   764 KBytes  6.25 Mbits/sec   34   25.5 KBytes
[  5]   1.00-2.00   sec   191 KBytes  1.56 Mbits/sec   22   7.07 KBytes
[  5]   2.00-3.00   sec   191 KBytes  1.56 Mbits/sec    9   7.07 KBytes
[  5]   3.00-4.00   sec   191 KBytes  1.56 Mbits/sec   10   7.07 KBytes
[  5]   4.00-5.00   sec   191 KBytes  1.56 Mbits/sec   14   7.07 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.49 MBytes  2.50 Mbits/sec   89             sender
[  5]   0.00-5.00   sec  1.17 MBytes  1.96 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 34298 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   898 KBytes  7.35 Mbits/sec    5    106 KBytes
[  5]   1.00-2.00   sec   389 KBytes  3.18 Mbits/sec   33   82.0 KBytes
[  5]   2.00-3.00   sec   382 KBytes  3.13 Mbits/sec   32   26.9 KBytes
[  5]   3.00-4.00   sec  0.00 Bytes  0.00 bits/sec    6   9.90 KBytes
[  5]   4.00-5.00   sec   382 KBytes  3.13 Mbits/sec   10   5.66 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  2.00 MBytes  3.36 Mbits/sec   86             sender
[  5]   0.00-5.01   sec  1.17 MBytes  1.96 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
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutPps\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: [1-9]\d*
OutRate\.[^=]+ = INTEGER: 4000000
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+
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutPackets."eth0" = INTEGER: 40017
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutPps."eth0" = INTEGER: 804
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBytes."eth0" = INTEGER: 5146946
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutDrops."eth0" = INTEGER: 42
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutKind."eth0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBps."eth0" = INTEGER: 228469
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutOverlimits."eth0" = INTEGER: 34271
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutRate."eth0" = INTEGER: 4000000
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: 19156
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassPackets."eth0".2 = INTEGER: 20861
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".1 = INTEGER: 1282773
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".2 = INTEGER: 3864173
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: 17700
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassOverlimits."eth0".2 = INTEGER: 16571
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPackets."eth0" = INTEGER: 118589
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPps."eth0" = INTEGER: 2416
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBytes."eth0" = INTEGER: 177843075
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInDrops."eth0" = INTEGER: 602
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInKind."eth0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBps."eth0" = INTEGER: 3534290
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 HTB
set service snmp community 'COMMUNITY2TEST!'
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set traffic control HTB type htb bandwidth 4
set traffic control HTB type htb class 1 bandwidth percentage 50
set traffic control HTB type htb class 2 bandwidth percentage 50
set traffic control HTB type htb default-class 2
set traffic control HTB type htb match 1 class 1
set traffic control HTB type htb match 1 ip protocol tcp
set traffic control HTB type htb match 1 ip source port 1234
set traffic control NETEM type network-emulator packet-loss 0.5

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

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.363/0.363/0.363/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 48172 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  12.6 MBytes   106 Mbits/sec   35   45.2 KBytes
[  5]   1.00-2.00   sec  12.9 MBytes   108 Mbits/sec   55   19.8 KBytes
[  5]   2.00-3.00   sec  11.7 MBytes  98.5 Mbits/sec   44   17.0 KBytes
[  5]   3.00-4.00   sec  11.7 MBytes  98.5 Mbits/sec   41   56.6 KBytes
[  5]   4.00-5.00   sec  12.3 MBytes   103 Mbits/sec   35   12.7 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  61.3 MBytes   103 Mbits/sec  210             sender
[  5]   0.00-5.00   sec  59.6 MBytes   100 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 46078 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.7 MBytes   123 Mbits/sec   40   19.8 KBytes
[  5]   1.00-2.00   sec  10.6 MBytes  88.6 Mbits/sec   55   12.7 KBytes
[  5]   2.00-3.00   sec  11.8 MBytes  99.0 Mbits/sec   46   43.8 KBytes
[  5]   3.00-4.00   sec  14.9 MBytes   125 Mbits/sec   54   17.0 KBytes
[  5]   4.00-5.00   sec  13.7 MBytes   115 Mbits/sec   56   14.1 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  65.7 MBytes   110 Mbits/sec  251             sender
[  5]   0.00-5.00   sec  64.3 MBytes   108 Mbits/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 44952 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   591 KBytes  4.84 Mbits/sec   31   19.8 KBytes
[  5]   1.00-2.00   sec   390 KBytes  3.20 Mbits/sec   10   5.66 KBytes
[  5]   2.00-3.00   sec   191 KBytes  1.56 Mbits/sec    7   7.07 KBytes
[  5]   3.00-4.00   sec   191 KBytes  1.56 Mbits/sec   17   7.07 KBytes
[  5]   4.00-5.00   sec   191 KBytes  1.56 Mbits/sec    6   9.90 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.52 MBytes  2.55 Mbits/sec   71             sender
[  5]   0.00-5.00   sec  1.17 MBytes  1.96 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 53080 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   615 KBytes  5.04 Mbits/sec   20   21.2 KBytes
[  5]   1.00-2.00   sec   127 KBytes  1.04 Mbits/sec    8   9.90 KBytes
[  5]   2.00-3.00   sec   255 KBytes  2.09 Mbits/sec   10   7.07 KBytes
[  5]   3.00-4.00   sec   255 KBytes  2.09 Mbits/sec    8   5.66 KBytes
[  5]   4.00-5.00   sec   255 KBytes  2.09 Mbits/sec   12   8.48 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.47 MBytes  2.47 Mbits/sec   58             sender
[  5]   0.00-5.00   sec  1.17 MBytes  1.96 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
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutPps\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: [1-9]\d*
OutRate\.[^=]+ = INTEGER: 4000000
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+
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutPackets."eth0"."100" = INTEGER: 40099
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutPps."eth0"."100" = INTEGER: 823
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBytes."eth0"."100" = INTEGER: 5151659
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutDrops."eth0"."100" = INTEGER: 47
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutKind."eth0"."100" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBps."eth0"."100" = INTEGER: 228983
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutOverlimits."eth0"."100" = INTEGER: 36012
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutRate."eth0"."100" = INTEGER: 4000000
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: 19155
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassPackets."eth0"."100".2 = INTEGER: 20944
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".1 = INTEGER: 1283077
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".2 = INTEGER: 3868582
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: 17500
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassOverlimits."eth0"."100".2 = INTEGER: 18512
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPackets."eth0"."100" = INTEGER: 90912
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPps."eth0"."100" = INTEGER: 1762
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBytes."eth0"."100" = INTEGER: 135966174
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInDrops."eth0"."100" = INTEGER: 469
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInKind."eth0"."100" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBps."eth0"."100" = INTEGER: 2560387
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 HTB
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 HTB type htb bandwidth 4
set traffic control HTB type htb class 1 bandwidth percentage 50
set traffic control HTB type htb class 2 bandwidth percentage 50
set traffic control HTB type htb default-class 2
set traffic control HTB type htb match 1 class 1
set traffic control HTB type htb match 1 ip protocol tcp
set traffic control HTB type htb match 1 ip source port 1234
set traffic control NETEM type network-emulator packet-loss 0.5

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

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.372/0.372/0.372/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 55636 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  10.5 MBytes  88.5 Mbits/sec   51   36.8 KBytes
[  5]   1.00-2.00   sec  11.1 MBytes  92.8 Mbits/sec   39   42.4 KBytes
[  5]   2.00-3.00   sec  10.1 MBytes  84.5 Mbits/sec   42   59.4 KBytes
[  5]   3.00-4.00   sec  11.3 MBytes  94.9 Mbits/sec   44   22.6 KBytes
[  5]   4.00-5.00   sec  11.6 MBytes  97.0 Mbits/sec   36   17.0 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  54.5 MBytes  91.5 Mbits/sec  212             sender
[  5]   0.00-5.00   sec  54.2 MBytes  90.8 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 41932 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  17.5 MBytes   147 Mbits/sec   54   17.0 KBytes
[  5]   1.00-2.00   sec  17.5 MBytes   146 Mbits/sec   73   18.4 KBytes
[  5]   2.00-3.00   sec  17.2 MBytes   144 Mbits/sec   46   19.8 KBytes
[  5]   3.00-4.00   sec  17.7 MBytes   149 Mbits/sec   81   15.6 KBytes
[  5]   4.00-5.00   sec  32.1 MBytes   269 Mbits/sec  105   18.4 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   102 MBytes   171 Mbits/sec  359             sender
[  5]   0.00-5.00   sec   101 MBytes   170 Mbits/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 43626 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   796 KBytes  6.52 Mbits/sec   48   18.4 KBytes
[  5]   1.00-2.00   sec   191 KBytes  1.56 Mbits/sec    7   7.07 KBytes
[  5]   2.00-3.00   sec   191 KBytes  1.56 Mbits/sec   13   8.48 KBytes
[  5]   3.00-4.00   sec   191 KBytes  1.56 Mbits/sec   15   5.66 KBytes
[  5]   4.00-5.00   sec   191 KBytes  1.56 Mbits/sec   14   7.07 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.52 MBytes  2.56 Mbits/sec   97             sender
[  5]   0.00-5.21   sec  1.22 MBytes  1.96 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 40532 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   707 KBytes  5.79 Mbits/sec   65   15.6 KBytes
[  5]   1.00-2.00   sec   201 KBytes  1.64 Mbits/sec   10   8.48 KBytes
[  5]   2.00-3.00   sec   191 KBytes  1.56 Mbits/sec   12   7.07 KBytes
[  5]   3.00-4.00   sec   382 KBytes  3.13 Mbits/sec   13   8.48 KBytes
[  5]   4.00-5.00   sec   191 KBytes  1.56 Mbits/sec   12   5.66 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.63 MBytes  2.74 Mbits/sec  112             sender
[  5]   0.00-5.21   sec  1.19 MBytes  1.91 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
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutPps\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: [1-9]\d*
OutRate\.[^=]+ = INTEGER: 4000000
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+
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutPackets."br0" = INTEGER: 40154
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutPps."br0" = INTEGER: 815
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBytes."br0" = INTEGER: 5251727
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutDrops."br0" = INTEGER: 57
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutKind."br0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBps."br0" = INTEGER: 228931
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutOverlimits."br0" = INTEGER: 33194
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutRate."br0" = INTEGER: 4000000
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: 19230
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassPackets."br0".2 = INTEGER: 20924
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".1 = INTEGER: 1283208
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".2 = INTEGER: 3968519
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: 17571
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassOverlimits."br0".2 = INTEGER: 15623
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPackets."br0" = INTEGER: 113725
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPps."br0" = INTEGER: 2425
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBytes."br0" = INTEGER: 170420740
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInDrops."br0" = INTEGER: 581
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInKind."br0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBps."br0" = INTEGER: 3558183
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 HTB
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 HTB type htb bandwidth 4
set traffic control HTB type htb class 1 bandwidth percentage 50
set traffic control HTB type htb class 2 bandwidth percentage 50
set traffic control HTB type htb default-class 2
set traffic control HTB type htb match 1 class 1
set traffic control HTB type htb match 1 ip protocol tcp
set traffic control HTB type htb match 1 ip source port 1234
set traffic control NETEM type network-emulator packet-loss 0.5

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

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.317/0.317/0.317/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 44582 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  12.7 MBytes   106 Mbits/sec   30   14.1 KBytes
[  5]   1.00-2.00   sec  11.9 MBytes   100 Mbits/sec   36   14.1 KBytes
[  5]   2.00-3.00   sec  11.6 MBytes  97.0 Mbits/sec   48   11.3 KBytes
[  5]   3.00-4.00   sec  12.7 MBytes   106 Mbits/sec   35   31.1 KBytes
[  5]   4.00-5.00   sec  13.4 MBytes   113 Mbits/sec   46   36.8 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  62.2 MBytes   104 Mbits/sec  195             sender
[  5]   0.00-5.00   sec  61.5 MBytes   103 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 57132 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  11.5 MBytes  96.7 Mbits/sec   47   14.1 KBytes
[  5]   1.00-2.00   sec  13.0 MBytes   109 Mbits/sec   46   46.7 KBytes
[  5]   2.00-3.00   sec  14.4 MBytes   120 Mbits/sec   52   22.6 KBytes
[  5]   3.00-4.00   sec  13.4 MBytes   113 Mbits/sec   46   24.0 KBytes
[  5]   4.00-5.00   sec  13.5 MBytes   113 Mbits/sec   56   17.0 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  65.8 MBytes   110 Mbits/sec  247             sender
[  5]   0.00-5.00   sec  65.4 MBytes   110 Mbits/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 46266 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   591 KBytes  4.84 Mbits/sec   14   24.0 KBytes
[  5]   1.00-2.00   sec   382 KBytes  3.13 Mbits/sec   14   7.07 KBytes
[  5]   2.00-3.00   sec   191 KBytes  1.56 Mbits/sec    8   8.48 KBytes
[  5]   3.00-4.00   sec   191 KBytes  1.56 Mbits/sec   14   4.24 KBytes
[  5]   4.00-5.00   sec   191 KBytes  1.56 Mbits/sec   11   5.66 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.51 MBytes  2.53 Mbits/sec   61             sender
[  5]   0.00-5.21   sec  1.22 MBytes  1.96 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 36608 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   758 KBytes  6.21 Mbits/sec   30   25.5 KBytes
[  5]   1.00-2.00   sec   191 KBytes  1.56 Mbits/sec   15   7.07 KBytes
[  5]   2.00-3.00   sec   191 KBytes  1.56 Mbits/sec   12   8.48 KBytes
[  5]   3.00-4.00   sec   191 KBytes  1.56 Mbits/sec   11   9.90 KBytes
[  5]   4.00-5.00   sec   191 KBytes  1.56 Mbits/sec   14   7.07 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.49 MBytes  2.49 Mbits/sec   82             sender
[  5]   0.00-5.21   sec  1.22 MBytes  1.96 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
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutPps\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: [1-9]\d*
OutRate\.[^=]+ = INTEGER: 4000000
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+
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutPackets."br0"."100" = INTEGER: 40204
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutPps."br0"."100" = INTEGER: 735
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBytes."br0"."100" = INTEGER: 5252573
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutDrops."br0"."100" = INTEGER: 54
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutKind."br0"."100" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBps."br0"."100" = INTEGER: 226096
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutOverlimits."br0"."100" = INTEGER: 35750
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutRate."br0"."100" = INTEGER: 4000000
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: 19202
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassPackets."br0"."100".2 = INTEGER: 21002
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".1 = INTEGER: 1283108
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".2 = INTEGER: 3969465
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: 17608
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassOverlimits."br0"."100".2 = INTEGER: 18142
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPackets."br0"."100" = INTEGER: 93249
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPps."br0"."100" = INTEGER: 1589
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBytes."br0"."100" = INTEGER: 139291484
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInDrops."br0"."100" = INTEGER: 450
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInKind."br0"."100" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBps."br0"."100" = INTEGER: 2286100
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 HTB
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 HTB type htb bandwidth 4
set traffic control HTB type htb class 1 bandwidth percentage 50
set traffic control HTB type htb class 2 bandwidth percentage 50
set traffic control HTB type htb default-class 2
set traffic control HTB type htb match 1 class 1
set traffic control HTB type htb match 1 ip protocol tcp
set traffic control HTB type htb match 1 ip source port 1234
set traffic control NETEM type network-emulator packet-loss 0.5

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

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.304/0.304/0.304/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 52472 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  11.6 MBytes  97.5 Mbits/sec   43   14.1 KBytes
[  5]   1.00-2.00   sec  9.94 MBytes  83.5 Mbits/sec   43   18.4 KBytes
[  5]   2.00-3.00   sec  11.9 MBytes   100 Mbits/sec   46   21.2 KBytes
[  5]   3.00-4.00   sec  11.4 MBytes  95.9 Mbits/sec   33   48.1 KBytes
[  5]   4.00-5.00   sec  10.4 MBytes  87.6 Mbits/sec   43   11.3 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  55.4 MBytes  92.9 Mbits/sec  208             sender
[  5]   0.00-5.00   sec  54.3 MBytes  91.0 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 35576 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  10.7 MBytes  90.0 Mbits/sec   41   31.1 KBytes
[  5]   1.00-2.00   sec  9.82 MBytes  82.4 Mbits/sec   34   31.1 KBytes
[  5]   2.00-3.00   sec  9.69 MBytes  81.3 Mbits/sec   40   29.7 KBytes
[  5]   3.00-4.00   sec  10.3 MBytes  86.5 Mbits/sec   32   17.0 KBytes
[  5]   4.00-5.00   sec  11.1 MBytes  93.3 Mbits/sec   46   36.8 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  51.7 MBytes  86.7 Mbits/sec  193             sender
[  5]   0.00-5.00   sec  51.5 MBytes  86.4 Mbits/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 40840 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   732 KBytes  6.00 Mbits/sec   14   24.0 KBytes
[  5]   1.00-2.00   sec   191 KBytes  1.56 Mbits/sec    8   9.90 KBytes
[  5]   2.00-3.00   sec   191 KBytes  1.56 Mbits/sec   12   7.07 KBytes
[  5]   3.00-4.00   sec   191 KBytes  1.56 Mbits/sec   14   4.24 KBytes
[  5]   4.00-5.00   sec   382 KBytes  3.13 Mbits/sec   14   5.66 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.65 MBytes  2.76 Mbits/sec   62             sender
[  5]   0.00-5.21   sec  1.22 MBytes  1.96 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 47034 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   718 KBytes  5.88 Mbits/sec    8   24.0 KBytes
[  5]   1.00-2.00   sec   191 KBytes  1.56 Mbits/sec   19   7.07 KBytes
[  5]   2.00-3.00   sec   191 KBytes  1.56 Mbits/sec    6   8.48 KBytes
[  5]   3.00-4.00   sec   191 KBytes  1.56 Mbits/sec    9   7.07 KBytes
[  5]   4.00-5.00   sec   191 KBytes  1.56 Mbits/sec   14   5.66 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.45 MBytes  2.43 Mbits/sec   56             sender
[  5]   0.00-5.21   sec  1.22 MBytes  1.96 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
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutPps\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: [1-9]\d*
OutRate\.[^=]+ = INTEGER: 4000000
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: 40237
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPps."bond0" = INTEGER: 815
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBytes."bond0" = INTEGER: 5252591
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutDrops."bond0" = INTEGER: 55
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutKind."bond0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBps."bond0" = INTEGER: 228764
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutOverlimits."bond0" = INTEGER: 36691
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutRate."bond0" = INTEGER: 4000000
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: 19162
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassPackets."bond0".2 = INTEGER: 21075
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".1 = INTEGER: 1282547
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".2 = INTEGER: 3970044
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: 17879
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassOverlimits."bond0".2 = INTEGER: 18812
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPackets."bond0" = INTEGER: 77827
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPps."bond0" = INTEGER: 1457
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBytes."bond0" = INTEGER: 116071640
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInDrops."bond0" = INTEGER: 407
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInKind."bond0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBps."bond0" = INTEGER: 2097916
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 HTB
set service snmp community 'COMMUNITY2TEST!'
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set traffic control HTB type htb bandwidth 4
set traffic control HTB type htb class 1 bandwidth percentage 50
set traffic control HTB type htb class 2 bandwidth percentage 50
set traffic control HTB type htb default-class 2
set traffic control HTB type htb match 1 class 1
set traffic control HTB type htb match 1 ip protocol tcp
set traffic control HTB type htb match 1 ip source port 1234
set traffic control NETEM type network-emulator packet-loss 0.5

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

--- 10.0.0.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.380/0.380/0.380/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 52312 connected to 10.0.0.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  25.5 MBytes   214 Mbits/sec   91   66.8 KBytes
[  5]   1.00-2.00   sec  11.9 MBytes  99.9 Mbits/sec   35   1.39 KBytes
[  5]   2.00-3.00   sec  36.2 MBytes   304 Mbits/sec  132   19.5 KBytes
[  5]   3.00-4.00   sec  45.5 MBytes   382 Mbits/sec  212   23.6 KBytes
[  5]   4.00-5.00   sec  58.5 MBytes   491 Mbits/sec  308    192 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   178 MBytes   298 Mbits/sec  778             sender
[  5]   0.00-5.00   sec   176 MBytes   296 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 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 59498 connected to 10.0.0.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  31.4 MBytes   263 Mbits/sec  144   54.2 KBytes
[  5]   1.00-2.00   sec  17.5 MBytes   147 Mbits/sec   51   57.0 KBytes
[  5]   2.00-3.00   sec  40.0 MBytes   336 Mbits/sec   98    145 KBytes
[  5]   3.00-4.00   sec   115 MBytes   965 Mbits/sec  499    175 KBytes
[  5]   4.00-5.00   sec  95.0 MBytes   797 Mbits/sec  310   54.2 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   299 MBytes   501 Mbits/sec  1102             sender
[  5]   0.00-5.00   sec   295 MBytes   496 Mbits/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 41912 connected to 10.0.0.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   840 KBytes  6.88 Mbits/sec   16   30.6 KBytes
[  5]   1.00-2.00   sec   188 KBytes  1.54 Mbits/sec   21   8.34 KBytes
[  5]   2.00-3.00   sec   250 KBytes  2.05 Mbits/sec   12   8.34 KBytes
[  5]   3.00-4.00   sec   188 KBytes  1.54 Mbits/sec   19   6.95 KBytes
[  5]   4.00-5.00   sec   188 KBytes  1.54 Mbits/sec   14   8.34 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.61 MBytes  2.71 Mbits/sec   82             sender
[  5]   0.00-5.00   sec  1.18 MBytes  1.98 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 39924 connected to 10.0.0.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   622 KBytes  5.09 Mbits/sec   23   20.9 KBytes
[  5]   1.00-2.00   sec   375 KBytes  3.08 Mbits/sec   12   6.95 KBytes
[  5]   2.00-3.00   sec   188 KBytes  1.54 Mbits/sec   11   6.95 KBytes
[  5]   3.00-4.00   sec   188 KBytes  1.54 Mbits/sec   10   8.34 KBytes
[  5]   4.00-5.00   sec   188 KBytes  1.54 Mbits/sec    8   6.95 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.52 MBytes  2.56 Mbits/sec   64             sender
[  5]   0.00-5.21   sec  1.23 MBytes  1.98 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
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutPps\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: [1-9]\d*
OutRate\.[^=]+ = INTEGER: 4000000
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: 47360
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutPps."tun0" = INTEGER: 936
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBytes."tun0" = INTEGER: 5028683
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutDrops."tun0" = INTEGER: 54
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutKind."tun0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBps."tun0" = INTEGER: 227688
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutOverlimits."tun0" = INTEGER: 33211
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutRate."tun0" = INTEGER: 4000000
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: 21131
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassPackets."tun0".2 = INTEGER: 26229
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".1 = INTEGER: 1109646
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".2 = INTEGER: 3919037
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: 10743
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassOverlimits."tun0".2 = INTEGER: 22468
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPackets."tun0" = INTEGER: 348505
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPps."tun0" = INTEGER: 7294
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBytes."tun0" = INTEGER: 513231942
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInDrops."tun0" = INTEGER: 379
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInKind."tun0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBps."tun0" = INTEGER: 10686727
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInOverlimits."tun0" = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInRate."tun0" = INTEGER: 0