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

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.522/0.522/0.522/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 38586 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  23.1 MBytes   193 Mbits/sec   89   24.0 KBytes
[  5]   1.00-2.00   sec  25.5 MBytes   214 Mbits/sec   88   9.90 KBytes
[  5]   2.00-3.00   sec  26.6 MBytes   223 Mbits/sec   94   41.0 KBytes
[  5]   3.00-4.00   sec  25.0 MBytes   210 Mbits/sec   83   72.1 KBytes
[  5]   4.00-5.00   sec  21.8 MBytes   183 Mbits/sec   96   32.5 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   122 MBytes   205 Mbits/sec  450             sender
[  5]   0.00-5.00   sec   121 MBytes   203 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 34082 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  24.4 MBytes   204 Mbits/sec   94   8.48 KBytes
[  5]   1.00-2.00   sec  35.2 MBytes   296 Mbits/sec  109   12.7 KBytes
[  5]   2.00-3.00   sec  27.0 MBytes   227 Mbits/sec  110   12.7 KBytes
[  5]   3.00-4.00   sec  33.1 MBytes   277 Mbits/sec  117   11.3 KBytes
[  5]   4.00-5.00   sec  27.0 MBytes   227 Mbits/sec  103   31.1 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   147 MBytes   246 Mbits/sec  533             sender
[  5]   0.00-5.00   sec   145 MBytes   243 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 45296 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   609 KBytes  4.99 Mbits/sec   17   42.4 KBytes
[  5]   1.00-2.00   sec   255 KBytes  2.09 Mbits/sec   14   8.48 KBytes
[  5]   2.00-3.00   sec   382 KBytes  3.13 Mbits/sec   10   7.07 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    9   7.07 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.59 MBytes  2.67 Mbits/sec   59             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 57652 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   645 KBytes  5.28 Mbits/sec   33   19.8 KBytes
[  5]   1.00-2.00   sec   191 KBytes  1.56 Mbits/sec   12   8.48 KBytes
[  5]   2.00-3.00   sec   382 KBytes  3.13 Mbits/sec    8   5.66 KBytes
[  5]   3.00-4.00   sec   191 KBytes  1.56 Mbits/sec    9   8.48 KBytes
[  5]   4.00-5.00   sec   191 KBytes  1.56 Mbits/sec   11   7.07 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.56 MBytes  2.62 Mbits/sec   73             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::telOSDxMonDBInterfacesEthernetTrafficControlOutPackets."eth0" = INTEGER: 39759
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutPps."eth0" = INTEGER: 744
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBytes."eth0" = INTEGER: 5250561
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutDrops."eth0" = INTEGER: 53
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutKind."eth0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBps."eth0" = INTEGER: 228518
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutOverlimits."eth0" = INTEGER: 37778
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: 18981
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassPackets."eth0".2 = INTEGER: 20778
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".1 = INTEGER: 1283079
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".2 = INTEGER: 3967482
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: 18505
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassOverlimits."eth0".2 = INTEGER: 19273
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPackets."eth0" = INTEGER: 193747
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPps."eth0" = INTEGER: 3368
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBytes."eth0" = INTEGER: 291318680
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInDrops."eth0" = INTEGER: 991
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInKind."eth0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBps."eth0" = INTEGER: 4960667
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.513 ms

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.513/0.513/0.513/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 38640 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  29.2 MBytes   245 Mbits/sec  101   41.0 KBytes
[  5]   1.00-2.00   sec  25.3 MBytes   212 Mbits/sec   90   25.5 KBytes
[  5]   2.00-3.00   sec  24.9 MBytes   209 Mbits/sec   85   18.4 KBytes
[  5]   3.00-4.00   sec  23.7 MBytes   199 Mbits/sec   90   24.0 KBytes
[  5]   4.00-5.00   sec  25.0 MBytes   210 Mbits/sec   91   9.90 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   128 MBytes   215 Mbits/sec  457             sender
[  5]   0.00-5.00   sec   127 MBytes   214 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 44802 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  22.7 MBytes   191 Mbits/sec   89   12.7 KBytes
[  5]   1.00-2.00   sec  26.6 MBytes   223 Mbits/sec   77   35.4 KBytes
[  5]   2.00-3.00   sec  24.9 MBytes   209 Mbits/sec   89   19.8 KBytes
[  5]   3.00-4.00   sec  29.3 MBytes   246 Mbits/sec   99   12.7 KBytes
[  5]   4.00-5.00   sec  29.0 MBytes   243 Mbits/sec  102   24.0 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   133 MBytes   222 Mbits/sec  456             sender
[  5]   0.00-5.00   sec   131 MBytes   220 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 34530 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   676 KBytes  5.54 Mbits/sec   41   22.6 KBytes
[  5]   1.00-2.00   sec   191 KBytes  1.56 Mbits/sec   17   7.07 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   15   7.07 KBytes
[  5]   4.00-5.00   sec   382 KBytes  3.13 Mbits/sec   15   7.07 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.59 MBytes  2.67 Mbits/sec   95             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 42368 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   549 KBytes  4.49 Mbits/sec   37   9.90 KBytes
[  5]   1.00-2.00   sec   382 KBytes  3.13 Mbits/sec   17   7.07 KBytes
[  5]   2.00-3.00   sec   191 KBytes  1.56 Mbits/sec   15   5.66 KBytes
[  5]   3.00-4.00   sec   191 KBytes  1.56 Mbits/sec   12   7.07 KBytes
[  5]   4.00-5.00   sec   191 KBytes  1.56 Mbits/sec   15   7.07 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.47 MBytes  2.46 Mbits/sec   96             sender
[  5]   0.00-5.22   sec  1.18 MBytes  1.90 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: 39882
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutPps."eth0"."100" = INTEGER: 748
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBytes."eth0"."100" = INTEGER: 5253782
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutDrops."eth0"."100" = INTEGER: 61
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutKind."eth0"."100" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBps."eth0"."100" = INTEGER: 229263
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutOverlimits."eth0"."100" = INTEGER: 37856
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: 19039
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassPackets."eth0"."100".2 = INTEGER: 20843
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".1 = INTEGER: 1283126
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".2 = INTEGER: 3970656
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: 18496
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassOverlimits."eth0"."100".2 = INTEGER: 19360
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPackets."eth0"."100" = INTEGER: 188490
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPps."eth0"."100" = INTEGER: 3207
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBytes."eth0"."100" = INTEGER: 283642689
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInDrops."eth0"."100" = INTEGER: 919
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInKind."eth0"."100" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBps."eth0"."100" = INTEGER: 4741918
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.582 ms

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.582/0.582/0.582/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 40506 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  25.7 MBytes   215 Mbits/sec  100   12.7 KBytes
[  5]   1.00-2.00   sec  26.7 MBytes   224 Mbits/sec   81   12.7 KBytes
[  5]   2.00-3.00   sec  26.3 MBytes   221 Mbits/sec  100   11.3 KBytes
[  5]   3.00-4.00   sec  25.7 MBytes   215 Mbits/sec  114   18.4 KBytes
[  5]   4.00-5.00   sec  31.9 MBytes   267 Mbits/sec  116   12.7 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   136 MBytes   229 Mbits/sec  511             sender
[  5]   0.00-5.00   sec   135 MBytes   227 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 52308 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  27.5 MBytes   231 Mbits/sec  103    133 KBytes
[  5]   1.00-2.00   sec  26.8 MBytes   225 Mbits/sec   99   14.1 KBytes
[  5]   2.00-3.00   sec  36.3 MBytes   304 Mbits/sec  106   8.48 KBytes
[  5]   3.00-4.00   sec  31.8 MBytes   267 Mbits/sec  112   8.48 KBytes
[  5]   4.00-5.00   sec  29.3 MBytes   246 Mbits/sec  109   9.90 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   152 MBytes   255 Mbits/sec  529             sender
[  5]   0.00-5.00   sec   150 MBytes   252 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 38270 connected to 192.168.100.2 port 1234
[ 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   7.07 KBytes
[  5]   2.00-3.00   sec   191 KBytes  1.56 Mbits/sec   12   4.24 KBytes
[  5]   3.00-4.00   sec   191 KBytes  1.56 Mbits/sec   14   2.83 KBytes
[  5]   4.00-5.00   sec   382 KBytes  3.13 Mbits/sec   14   7.07 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.63 MBytes  2.74 Mbits/sec  115             sender
[  5]   0.00-5.22   sec  1.19 MBytes  1.91 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 58346 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   755 KBytes  6.19 Mbits/sec   45   17.0 KBytes
[  5]   1.00-2.00   sec   191 KBytes  1.56 Mbits/sec   16   7.07 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   13   7.07 KBytes
[  5]   4.00-5.00   sec   191 KBytes  1.56 Mbits/sec   14   8.48 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.48 MBytes  2.49 Mbits/sec  100             sender
[  5]   0.00-5.21   sec  1.21 MBytes  1.95 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: 39683
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutPps."br0" = INTEGER: 748
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBytes."br0" = INTEGER: 5252092
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutDrops."br0" = INTEGER: 61
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutKind."br0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBps."br0" = INTEGER: 229339
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutOverlimits."br0" = INTEGER: 37679
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: 18970
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassPackets."br0".2 = INTEGER: 20713
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".1 = INTEGER: 1283387
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".2 = INTEGER: 3968705
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: 18476
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassOverlimits."br0".2 = INTEGER: 19203
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPackets."br0" = INTEGER: 208157
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPps."br0" = INTEGER: 3610
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBytes."br0" = INTEGER: 313392396
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInDrops."br0" = INTEGER: 1047
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInKind."br0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBps."br0" = INTEGER: 5352919
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.616 ms

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.616/0.616/0.616/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 47104 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  26.4 MBytes   222 Mbits/sec   93   14.1 KBytes
[  5]   1.00-2.00   sec  23.1 MBytes   194 Mbits/sec   89   12.7 KBytes
[  5]   2.00-3.00   sec  26.1 MBytes   219 Mbits/sec   75   12.7 KBytes
[  5]   3.00-4.00   sec  23.7 MBytes   199 Mbits/sec   93   11.3 KBytes
[  5]   4.00-5.00   sec  21.9 MBytes   183 Mbits/sec  101   14.1 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   121 MBytes   203 Mbits/sec  451             sender
[  5]   0.00-5.00   sec   121 MBytes   202 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 44062 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  28.7 MBytes   241 Mbits/sec   97   7.07 KBytes
[  5]   1.00-2.00   sec  32.5 MBytes   273 Mbits/sec  126   19.8 KBytes
[  5]   2.00-3.00   sec  32.3 MBytes   271 Mbits/sec   99   17.0 KBytes
[  5]   3.00-4.00   sec  32.2 MBytes   270 Mbits/sec  118   19.8 KBytes
[  5]   4.00-5.00   sec  32.1 MBytes   269 Mbits/sec  121   8.48 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   158 MBytes   265 Mbits/sec  561             sender
[  5]   0.00-5.00   sec   156 MBytes   261 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 54152 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   766 KBytes  6.28 Mbits/sec   27   38.2 KBytes
[  5]   1.00-2.00   sec   199 KBytes  1.63 Mbits/sec   12   11.3 KBytes
[  5]   2.00-3.00   sec   191 KBytes  1.56 Mbits/sec    7   9.90 KBytes
[  5]   3.00-4.00   sec   191 KBytes  1.56 Mbits/sec    8   7.07 KBytes
[  5]   4.00-5.00   sec   191 KBytes  1.56 Mbits/sec    9   7.07 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.50 MBytes  2.52 Mbits/sec   63             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 50880 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   672 KBytes  5.50 Mbits/sec   31   29.7 KBytes
[  5]   1.00-2.00   sec   255 KBytes  2.09 Mbits/sec   20   5.66 KBytes
[  5]   2.00-3.00   sec   191 KBytes  1.56 Mbits/sec    8   8.48 KBytes
[  5]   3.00-4.00   sec   382 KBytes  3.13 Mbits/sec    8   7.07 KBytes
[  5]   4.00-5.00   sec   191 KBytes  1.56 Mbits/sec    8   9.90 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.65 MBytes  2.77 Mbits/sec   75             sender
[  5]   0.00-5.22   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: 39773
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutPps."br0"."100" = INTEGER: 741
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBytes."br0"."100" = INTEGER: 5253306
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutDrops."br0"."100" = INTEGER: 50
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutKind."br0"."100" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBps."br0"."100" = INTEGER: 229207
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutOverlimits."br0"."100" = INTEGER: 37760
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: 19023
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassPackets."br0"."100".2 = INTEGER: 20750
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".1 = INTEGER: 1283021
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".2 = INTEGER: 3970285
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: 18497
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassOverlimits."br0"."100".2 = INTEGER: 19263
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPackets."br0"."100" = INTEGER: 201859
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPps."br0"."100" = INTEGER: 3545
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBytes."br0"."100" = INTEGER: 303305015
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInDrops."br0"."100" = INTEGER: 1017
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInKind."br0"."100" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBps."br0"."100" = INTEGER: 5205189
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.484 ms

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.484/0.484/0.484/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 50782 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  24.0 MBytes   201 Mbits/sec   72   19.8 KBytes
[  5]   1.00-2.00   sec  25.8 MBytes   216 Mbits/sec   97   18.4 KBytes
[  5]   2.00-3.00   sec  23.3 MBytes   195 Mbits/sec   79   50.9 KBytes
[  5]   3.00-4.00   sec  25.0 MBytes   210 Mbits/sec   81   14.1 KBytes
[  5]   4.00-5.00   sec  24.3 MBytes   204 Mbits/sec   96   14.1 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   122 MBytes   205 Mbits/sec  425             sender
[  5]   0.00-5.00   sec   122 MBytes   204 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 59076 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  22.9 MBytes   192 Mbits/sec   85   18.4 KBytes
[  5]   1.00-2.00   sec  25.0 MBytes   210 Mbits/sec   84   9.90 KBytes
[  5]   2.00-3.00   sec  22.4 MBytes   188 Mbits/sec   91   35.4 KBytes
[  5]   3.00-4.00   sec  31.8 MBytes   266 Mbits/sec  126   25.5 KBytes
[  5]   4.00-5.00   sec  33.9 MBytes   285 Mbits/sec  120   28.3 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   136 MBytes   228 Mbits/sec  506             sender
[  5]   0.00-5.00   sec   135 MBytes   226 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 43096 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   518 KBytes  4.24 Mbits/sec   15   14.1 KBytes
[  5]   1.00-2.00   sec   255 KBytes  2.09 Mbits/sec   14   4.24 KBytes
[  5]   2.00-3.00   sec   255 KBytes  2.09 Mbits/sec   11   5.66 KBytes
[  5]   3.00-4.00   sec   255 KBytes  2.09 Mbits/sec   11   7.07 KBytes
[  5]   4.00-5.00   sec   255 KBytes  2.09 Mbits/sec   16   7.07 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.50 MBytes  2.52 Mbits/sec   67             sender
[  5]   0.00-5.22   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 42492 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   580 KBytes  4.75 Mbits/sec   16   22.6 KBytes
[  5]   1.00-2.00   sec   382 KBytes  3.13 Mbits/sec    8   4.24 KBytes
[  5]   2.00-3.00   sec   191 KBytes  1.56 Mbits/sec   14   5.66 KBytes
[  5]   3.00-4.00   sec   191 KBytes  1.56 Mbits/sec   10   5.66 KBytes
[  5]   4.00-5.00   sec   191 KBytes  1.56 Mbits/sec   10   7.07 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.50 MBytes  2.51 Mbits/sec   58             sender
[  5]   0.00-5.22   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: 39815
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPps."bond0" = INTEGER: 740
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBytes."bond0" = INTEGER: 5255586
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutDrops."bond0" = INTEGER: 58
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutKind."bond0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBps."bond0" = INTEGER: 229515
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutOverlimits."bond0" = INTEGER: 37877
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: 19034
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassPackets."bond0".2 = INTEGER: 20781
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".1 = INTEGER: 1283049
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".2 = INTEGER: 3972537
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: 18535
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassOverlimits."bond0".2 = INTEGER: 19342
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPackets."bond0" = INTEGER: 187278
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPps."bond0" = INTEGER: 3252
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBytes."bond0" = INTEGER: 281767350
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInDrops."bond0" = INTEGER: 938
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInKind."bond0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBps."bond0" = INTEGER: 4807110
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.569 ms

--- 10.0.0.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.569/0.569/0.569/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 36768 connected to 10.0.0.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   138 MBytes  1.16 Gbits/sec  291    236 KBytes
[  5]   1.00-2.00   sec  97.5 MBytes   818 Mbits/sec  391   57.0 KBytes
[  5]   2.00-3.00   sec   179 MBytes  1.50 Gbits/sec  621   54.2 KBytes
[  5]   3.00-4.00   sec   129 MBytes  1.08 Gbits/sec  559    224 KBytes
[  5]   4.00-5.00   sec   116 MBytes   975 Mbits/sec  343    152 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   659 MBytes  1.11 Gbits/sec  2205             sender
[  5]   0.00-5.00   sec   657 MBytes  1.10 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 49102 connected to 10.0.0.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   124 MBytes  1.04 Gbits/sec  401    160 KBytes
[  5]   1.00-2.00   sec   136 MBytes  1.14 Gbits/sec  261    161 KBytes
[  5]   2.00-3.00   sec  93.8 MBytes   786 Mbits/sec  499    128 KBytes
[  5]   3.00-4.00   sec   145 MBytes  1.22 Gbits/sec  674   40.3 KBytes
[  5]   4.00-5.00   sec   101 MBytes   849 Mbits/sec  372   72.3 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   600 MBytes  1.01 Gbits/sec  2207             sender
[  5]   0.00-5.00   sec   597 MBytes  1.00 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 57832 connected to 10.0.0.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   647 KBytes  5.29 Mbits/sec   44   23.6 KBytes
[  5]   1.00-2.00   sec   188 KBytes  1.54 Mbits/sec   24   5.56 KBytes
[  5]   2.00-3.00   sec   375 KBytes  3.08 Mbits/sec    9   9.73 KBytes
[  5]   3.00-4.00   sec   188 KBytes  1.54 Mbits/sec   14   8.34 KBytes
[  5]   4.00-5.00   sec   188 KBytes  1.54 Mbits/sec    8   11.1 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.55 MBytes  2.60 Mbits/sec   99             sender
[  5]   0.00-5.21   sec  1.23 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 38818 connected to 10.0.0.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   723 KBytes  5.92 Mbits/sec   52   23.6 KBytes
[  5]   1.00-2.00   sec   188 KBytes  1.54 Mbits/sec   35   8.34 KBytes
[  5]   2.00-3.00   sec   188 KBytes  1.54 Mbits/sec    8   6.95 KBytes
[  5]   3.00-4.00   sec   188 KBytes  1.54 Mbits/sec   13   6.95 KBytes
[  5]   4.00-5.00   sec   375 KBytes  3.08 Mbits/sec    9   6.95 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.62 MBytes  2.72 Mbits/sec  117             sender
[  5]   0.00-5.21   sec  1.22 MBytes  1.97 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: 50649
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutPps."tun0" = INTEGER: 917
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBytes."tun0" = INTEGER: 5251717
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutDrops."tun0" = INTEGER: 55
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutKind."tun0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBps."tun0" = INTEGER: 229060
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutOverlimits."tun0" = INTEGER: 39517
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: 24398
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassPackets."tun0".2 = INTEGER: 26251
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".1 = INTEGER: 1282665
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".2 = INTEGER: 3969052
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: 19288
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassOverlimits."tun0".2 = INTEGER: 20229
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPackets."tun0" = INTEGER: 924303
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPps."tun0" = INTEGER: 14712
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBytes."tun0" = INTEGER: 1363197789
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInDrops."tun0" = INTEGER: 492
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInKind."tun0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBps."tun0" = INTEGER: 21644005
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInOverlimits."tun0" = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInRate."tun0" = INTEGER: 0