Tc Snmp Monitor

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

Test Traffic Control OIDs On Ethernet Interface

Description

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

Scenario

Step 1: Set the following configuration in DUT0 :

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

Step 2: Set the following configuration in DUT1 :

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

Step 3: Ping IP address 192.168.100.1 from DUT1:

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

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.076/1.076/1.076/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 42054 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   139 MBytes  1.16 Gbits/sec  501   46.7 KBytes
[  5]   1.00-2.00   sec   141 MBytes  1.18 Gbits/sec  543   59.4 KBytes
[  5]   2.00-3.00   sec   141 MBytes  1.18 Gbits/sec  509   42.4 KBytes
[  5]   3.00-4.00   sec   157 MBytes  1.31 Gbits/sec  623   28.3 KBytes
[  5]   4.00-5.00   sec   155 MBytes  1.30 Gbits/sec  595   38.2 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   731 MBytes  1.23 Gbits/sec  2771             sender
[  5]   0.00-5.00   sec   731 MBytes  1.23 Gbits/sec                  receiver

iperf Done.

Step 5: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 4321
admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 4321 parallel 1
Expect this output in DUT1:
Connecting to host 192.168.100.1, port 4321
[  5] local 192.168.100.2 port 40122 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   165 MBytes  1.38 Gbits/sec  602   48.1 KBytes
[  5]   1.00-2.00   sec   156 MBytes  1.31 Gbits/sec  579   15.6 KBytes
[  5]   2.00-3.00   sec   159 MBytes  1.33 Gbits/sec  544   18.4 KBytes
[  5]   3.00-4.00   sec   169 MBytes  1.42 Gbits/sec  623   19.8 KBytes
[  5]   4.00-5.00   sec   224 MBytes  1.88 Gbits/sec  711   36.8 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   872 MBytes  1.46 Gbits/sec  3059             sender
[  5]   0.00-5.00   sec   871 MBytes  1.46 Gbits/sec                  receiver

iperf Done.

Step 6: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 1234
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 1234 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 1234
[  5] local 192.168.100.1 port 47126 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  13.9 MBytes   116 Mbits/sec  167   94.7 KBytes
[  5]   1.00-2.00   sec  11.7 MBytes  98.5 Mbits/sec  102   70.7 KBytes
[  5]   2.00-3.00   sec  11.2 MBytes  93.8 Mbits/sec   78   63.6 KBytes
[  5]   3.00-4.00   sec  11.7 MBytes  98.5 Mbits/sec   70   84.8 KBytes
[  5]   4.00-5.00   sec  11.2 MBytes  93.8 Mbits/sec   78   94.7 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.7 MBytes   100 Mbits/sec  495             sender
[  5]   0.00-5.00   sec  58.4 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

Step 7: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 4321
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 4321 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 4321
[  5] local 192.168.100.1 port 57414 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.5 MBytes   121 Mbits/sec  187   93.3 KBytes
[  5]   1.00-2.00   sec  11.2 MBytes  94.4 Mbits/sec   59   90.5 KBytes
[  5]   2.00-3.00   sec  11.2 MBytes  93.8 Mbits/sec   72   87.7 KBytes
[  5]   3.00-4.00   sec  11.8 MBytes  99.1 Mbits/sec   82   91.9 KBytes
[  5]   4.00-5.00   sec  11.2 MBytes  93.8 Mbits/sec   90   96.2 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.9 MBytes   100 Mbits/sec  490             sender
[  5]   0.00-5.00   sec  58.4 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

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

OutKind\.[^=]+ = STRING: (htb|ceetm)
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: \d+
OutRate\.[^=]+ = INTEGER: 100000000
InPps\.[^=]+ = INTEGER: [1-9]\d*
InDrops\.[^=]+ = INTEGER: [1-9]\d*
InOverlimits\.[^=]+ = INTEGER: \d+
InRate\.[^=]+ = INTEGER: 0
OutClassPackets\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassPackets\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassDrops\.[^=]+\.1 = INTEGER: \d+
OutClassDrops\.[^=]+\.2 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.1 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.2 = INTEGER: \d+
OutPps\.[^=]+ = INTEGER: [1-9]\d*
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutPackets."eth0" = INTEGER: 260658
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutPps."eth0" = INTEGER: 9434
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBytes."eth0" = INTEGER: 140182238
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutDrops."eth0" = INTEGER: 35
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutKind."eth0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBps."eth0" = INTEGER: 9345410
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutOverlimits."eth0" = INTEGER: 7913
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutRate."eth0" = INTEGER: 100000000
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassTag."eth0".1 = INTEGER: 1
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassTag."eth0".2 = INTEGER: 2
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassPackets."eth0".1 = INTEGER: 78498
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassPackets."eth0".2 = INTEGER: 182160
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".1 = INTEGER: 5287462
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".2 = INTEGER: 134894776
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassDrops."eth0".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassDrops."eth0".2 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassOverlimits."eth0".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassOverlimits."eth0".2 = INTEGER: 4164
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPackets."eth0" = INTEGER: 1168980
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPps."eth0" = INTEGER: 22733
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBytes."eth0" = INTEGER: 1756650847
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInDrops."eth0" = INTEGER: 5868
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInKind."eth0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBps."eth0" = INTEGER: 33501839
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInOverlimits."eth0" = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInRate."eth0" = INTEGER: 0

Test Traffic Control OIDs On Ethernet VIF-S Interface

Description

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

Scenario

Step 1: Set the following configuration in DUT0 :

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

Step 2: Set the following configuration in DUT1 :

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

Step 3: Ping IP address 192.168.100.1 from DUT1:

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

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.656/0.656/0.656/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 38792 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   222 MBytes  1.86 Gbits/sec  819   28.3 KBytes
[  5]   1.00-2.00   sec   201 MBytes  1.69 Gbits/sec  712   58.0 KBytes
[  5]   2.00-3.00   sec   155 MBytes  1.30 Gbits/sec  550   17.0 KBytes
[  5]   3.00-4.00   sec   154 MBytes  1.29 Gbits/sec  557   39.6 KBytes
[  5]   4.00-5.00   sec   197 MBytes  1.65 Gbits/sec  674   48.1 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   929 MBytes  1.56 Gbits/sec  3312             sender
[  5]   0.00-5.00   sec   929 MBytes  1.56 Gbits/sec                  receiver

iperf Done.

Step 5: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 4321
admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 4321 parallel 1
Expect this output in DUT1:
Connecting to host 192.168.100.1, port 4321
[  5] local 192.168.100.2 port 52484 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   188 MBytes  1.58 Gbits/sec  652   41.0 KBytes
[  5]   1.00-2.00   sec   133 MBytes  1.12 Gbits/sec  497   39.6 KBytes
[  5]   2.00-3.00   sec   193 MBytes  1.62 Gbits/sec  699   39.6 KBytes
[  5]   3.00-4.00   sec   168 MBytes  1.41 Gbits/sec  600   31.1 KBytes
[  5]   4.00-5.00   sec   143 MBytes  1.20 Gbits/sec  535   39.6 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   825 MBytes  1.38 Gbits/sec  2983             sender
[  5]   0.00-5.00   sec   824 MBytes  1.38 Gbits/sec                  receiver

iperf Done.

Step 6: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 1234
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 1234 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 1234
[  5] local 192.168.100.1 port 45252 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.2 MBytes   119 Mbits/sec  168   87.7 KBytes
[  5]   1.00-2.00   sec  11.2 MBytes  94.4 Mbits/sec   74   91.9 KBytes
[  5]   2.00-3.00   sec  11.5 MBytes  96.4 Mbits/sec  102   56.6 KBytes
[  5]   3.00-4.00   sec  11.1 MBytes  92.8 Mbits/sec   48   91.9 KBytes
[  5]   4.00-5.00   sec  11.7 MBytes  98.5 Mbits/sec   73   94.7 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.8 MBytes   100 Mbits/sec  465             sender
[  5]   0.00-5.00   sec  58.4 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

Step 7: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 4321
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 4321 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 4321
[  5] local 192.168.100.1 port 48930 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  13.9 MBytes   116 Mbits/sec  157   94.7 KBytes
[  5]   1.00-2.00   sec  11.9 MBytes  99.6 Mbits/sec   97   72.1 KBytes
[  5]   2.00-3.00   sec  11.2 MBytes  94.4 Mbits/sec   74   72.1 KBytes
[  5]   3.00-4.00   sec  11.5 MBytes  96.4 Mbits/sec   70   82.0 KBytes
[  5]   4.00-5.00   sec  11.1 MBytes  93.3 Mbits/sec   74   86.3 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.6 MBytes   100 Mbits/sec  472             sender
[  5]   0.00-5.00   sec  58.4 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

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

OutKind\.[^=]+ = STRING: (htb|ceetm)
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: \d+
OutRate\.[^=]+ = INTEGER: 100000000
InPps\.[^=]+ = INTEGER: [1-9]\d*
InDrops\.[^=]+ = INTEGER: [1-9]\d*
InOverlimits\.[^=]+ = INTEGER: \d+
InRate\.[^=]+ = INTEGER: 0
OutClassPackets\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassPackets\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassDrops\.[^=]+\.1 = INTEGER: \d+
OutClassDrops\.[^=]+\.2 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.1 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.2 = INTEGER: \d+
OutPps\.[^=]+ = INTEGER: [1-9]\d*
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutPackets."eth0"."100" = INTEGER: 261935
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutPps."eth0"."100" = INTEGER: 9084
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBytes."eth0"."100" = INTEGER: 140265804
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutDrops."eth0"."100" = INTEGER: 35
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutKind."eth0"."100" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBps."eth0"."100" = INTEGER: 9407690
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutOverlimits."eth0"."100" = INTEGER: 7804
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutRate."eth0"."100" = INTEGER: 100000000
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassTag."eth0"."100".1 = INTEGER: 1
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassTag."eth0"."100".2 = INTEGER: 2
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassPackets."eth0"."100".1 = INTEGER: 98015
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassPackets."eth0"."100".2 = INTEGER: 163920
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".1 = INTEGER: 6590803
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".2 = INTEGER: 133675001
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassDrops."eth0"."100".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassDrops."eth0"."100".2 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassOverlimits."eth0"."100".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassOverlimits."eth0"."100".2 = INTEGER: 4100
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPackets."eth0"."100" = INTEGER: 1278080
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPps."eth0"."100" = INTEGER: 22572
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBytes."eth0"."100" = INTEGER: 1922333395
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInDrops."eth0"."100" = INTEGER: 6339
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInKind."eth0"."100" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBps."eth0"."100" = INTEGER: 33292939
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInOverlimits."eth0"."100" = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInRate."eth0"."100" = INTEGER: 0

Test Traffic Control OIDs On Bridge Interface

Description

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

Scenario

Step 1: Set the following configuration in DUT0 :

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

Step 2: Set the following configuration in DUT1 :

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

Step 3: Ping IP address 192.168.100.1 from DUT1:

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

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.754/0.754/0.754/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 48988 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   209 MBytes  1.76 Gbits/sec  709   32.5 KBytes
[  5]   1.00-2.00   sec   198 MBytes  1.66 Gbits/sec  726   42.4 KBytes
[  5]   2.00-3.00   sec   160 MBytes  1.35 Gbits/sec  615   21.2 KBytes
[  5]   3.00-4.00   sec   118 MBytes   988 Mbits/sec  446   33.9 KBytes
[  5]   4.00-5.00   sec  80.8 MBytes   678 Mbits/sec  296   14.1 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   766 MBytes  1.29 Gbits/sec  2792             sender
[  5]   0.00-5.00   sec   766 MBytes  1.28 Gbits/sec                  receiver

iperf Done.

Step 5: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 4321
admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 4321 parallel 1
Expect this output in DUT1:
Connecting to host 192.168.100.1, port 4321
[  5] local 192.168.100.2 port 36486 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   117 MBytes   983 Mbits/sec  425   33.9 KBytes
[  5]   1.00-2.00   sec   132 MBytes  1.11 Gbits/sec  485   25.5 KBytes
[  5]   2.00-3.00   sec   147 MBytes  1.23 Gbits/sec  536   28.3 KBytes
[  5]   3.00-4.00   sec   149 MBytes  1.25 Gbits/sec  556   26.9 KBytes
[  5]   4.00-5.01   sec   153 MBytes  1.26 Gbits/sec  520   49.5 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.01   sec   698 MBytes  1.17 Gbits/sec  2522             sender
[  5]   0.00-5.01   sec   697 MBytes  1.17 Gbits/sec                  receiver

iperf Done.

Step 6: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 1234
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 1234 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 1234
[  5] local 192.168.100.1 port 41832 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  13.9 MBytes   117 Mbits/sec  170   96.2 KBytes
[  5]   1.00-2.00   sec  11.8 MBytes  99.0 Mbits/sec   68   96.2 KBytes
[  5]   2.00-3.00   sec  11.5 MBytes  96.4 Mbits/sec  105   69.3 KBytes
[  5]   3.00-4.00   sec  11.2 MBytes  94.4 Mbits/sec   68   72.1 KBytes
[  5]   4.00-5.00   sec  11.2 MBytes  94.3 Mbits/sec   67   74.9 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.7 MBytes   100 Mbits/sec  478             sender
[  5]   0.00-5.00   sec  58.4 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

Step 7: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 4321
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 4321 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 4321
[  5] local 192.168.100.1 port 41364 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  13.6 MBytes   114 Mbits/sec  127    102 KBytes
[  5]   1.00-2.00   sec  11.7 MBytes  98.1 Mbits/sec   67   96.2 KBytes
[  5]   2.00-3.00   sec  11.2 MBytes  93.8 Mbits/sec   93   70.7 KBytes
[  5]   3.00-4.00   sec  11.7 MBytes  98.0 Mbits/sec   83   63.6 KBytes
[  5]   4.00-5.00   sec  11.2 MBytes  94.3 Mbits/sec   59   73.5 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.4 MBytes  99.6 Mbits/sec  429             sender
[  5]   0.00-5.00   sec  58.5 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

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

OutKind\.[^=]+ = STRING: (htb|ceetm)
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: \d+
OutRate\.[^=]+ = INTEGER: 100000000
InPps\.[^=]+ = INTEGER: [1-9]\d*
InDrops\.[^=]+ = INTEGER: [1-9]\d*
InOverlimits\.[^=]+ = INTEGER: \d+
InRate\.[^=]+ = INTEGER: 0
OutClassPackets\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassPackets\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassDrops\.[^=]+\.1 = INTEGER: \d+
OutClassDrops\.[^=]+\.2 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.1 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.2 = INTEGER: \d+
OutPps\.[^=]+ = INTEGER: [1-9]\d*
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutPackets."br0" = INTEGER: 231383
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutPps."br0" = INTEGER: 8554
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBytes."br0" = INTEGER: 138184752
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutDrops."br0" = INTEGER: 35
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutKind."br0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBps."br0" = INTEGER: 9249713
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutOverlimits."br0" = INTEGER: 8038
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutRate."br0" = INTEGER: 100000000
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassTag."br0".1 = INTEGER: 1
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassTag."br0".2 = INTEGER: 2
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassPackets."br0".1 = INTEGER: 78848
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassPackets."br0".2 = INTEGER: 152535
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".1 = INTEGER: 5309671
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".2 = INTEGER: 132875081
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassDrops."br0".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassDrops."br0".2 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassOverlimits."br0".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassOverlimits."br0".2 = INTEGER: 4230
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPackets."br0" = INTEGER: 1068263
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPps."br0" = INTEGER: 19488
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBytes."br0" = INTEGER: 1605007194
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInDrops."br0" = INTEGER: 5354
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInKind."br0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBps."br0" = INTEGER: 28667739
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInOverlimits."br0" = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInRate."br0" = INTEGER: 0

Test Traffic Control OIDs On Bridge VIF-S Interface

Description

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

Scenario

Step 1: Set the following configuration in DUT0 :

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

Step 2: Set the following configuration in DUT1 :

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

Step 3: Ping IP address 192.168.100.1 from DUT1:

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

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.452/0.452/0.452/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 47634 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   165 MBytes  1.38 Gbits/sec  586   33.9 KBytes
[  5]   1.00-2.00   sec   132 MBytes  1.10 Gbits/sec  501   36.8 KBytes
[  5]   2.00-3.00   sec   161 MBytes  1.35 Gbits/sec  609   29.7 KBytes
[  5]   3.00-4.00   sec   150 MBytes  1.25 Gbits/sec  508   36.8 KBytes
[  5]   4.00-5.00   sec   195 MBytes  1.63 Gbits/sec  678   36.8 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   801 MBytes  1.34 Gbits/sec  2882             sender
[  5]   0.00-5.00   sec   801 MBytes  1.34 Gbits/sec                  receiver

iperf Done.

Step 5: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 4321
admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 4321 parallel 1
Expect this output in DUT1:
Connecting to host 192.168.100.1, port 4321
[  5] local 192.168.100.2 port 41166 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   227 MBytes  1.91 Gbits/sec  834   38.2 KBytes
[  5]   1.00-2.00   sec   207 MBytes  1.74 Gbits/sec  776   22.6 KBytes
[  5]   2.00-3.00   sec   171 MBytes  1.43 Gbits/sec  626   52.3 KBytes
[  5]   3.00-4.00   sec   155 MBytes  1.30 Gbits/sec  597   39.6 KBytes
[  5]   4.00-5.00   sec   151 MBytes  1.26 Gbits/sec  551   50.9 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   912 MBytes  1.53 Gbits/sec  3384             sender
[  5]   0.00-5.00   sec   911 MBytes  1.53 Gbits/sec                  receiver

iperf Done.

Step 6: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 1234
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 1234 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 1234
[  5] local 192.168.100.1 port 49816 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  13.8 MBytes   116 Mbits/sec  140   66.5 KBytes
[  5]   1.00-2.00   sec  11.3 MBytes  94.9 Mbits/sec   75   66.5 KBytes
[  5]   2.00-3.00   sec  11.3 MBytes  94.9 Mbits/sec   35   77.8 KBytes
[  5]   3.00-4.00   sec  11.7 MBytes  98.5 Mbits/sec   42   91.9 KBytes
[  5]   4.00-5.00   sec  11.4 MBytes  95.4 Mbits/sec   63   99.0 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.6 MBytes  99.9 Mbits/sec  355             sender
[  5]   0.00-5.00   sec  58.5 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

Step 7: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 4321
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 4321 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 4321
[  5] local 192.168.100.1 port 41150 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.1 MBytes   118 Mbits/sec  167   83.4 KBytes
[  5]   1.00-2.00   sec  11.1 MBytes  93.3 Mbits/sec   73   86.3 KBytes
[  5]   2.00-3.00   sec  11.9 MBytes  99.6 Mbits/sec   71   89.1 KBytes
[  5]   3.00-4.00   sec  11.4 MBytes  95.4 Mbits/sec   73   90.5 KBytes
[  5]   4.00-5.00   sec  11.0 MBytes  92.3 Mbits/sec   95   69.3 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.5 MBytes  99.8 Mbits/sec  479             sender
[  5]   0.00-5.00   sec  58.4 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

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

OutKind\.[^=]+ = STRING: (htb|ceetm)
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: \d+
OutRate\.[^=]+ = INTEGER: 100000000
InPps\.[^=]+ = INTEGER: [1-9]\d*
InDrops\.[^=]+ = INTEGER: [1-9]\d*
InOverlimits\.[^=]+ = INTEGER: \d+
InRate\.[^=]+ = INTEGER: 0
OutClassPackets\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassPackets\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassDrops\.[^=]+\.1 = INTEGER: \d+
OutClassDrops\.[^=]+\.2 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.1 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.2 = INTEGER: \d+
OutPps\.[^=]+ = INTEGER: [1-9]\d*
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutPackets."br0"."100" = INTEGER: 250434
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutPps."br0"."100" = INTEGER: 9055
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBytes."br0"."100" = INTEGER: 139514215
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutDrops."br0"."100" = INTEGER: 32
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutKind."br0"."100" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBps."br0"."100" = INTEGER: 9234959
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutOverlimits."br0"."100" = INTEGER: 7652
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutRate."br0"."100" = INTEGER: 100000000
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassTag."br0"."100".1 = INTEGER: 1
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassTag."br0"."100".2 = INTEGER: 2
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassPackets."br0"."100".1 = INTEGER: 75986
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassPackets."br0"."100".2 = INTEGER: 174448
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".1 = INTEGER: 5121714
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".2 = INTEGER: 134392501
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassDrops."br0"."100".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassDrops."br0"."100".2 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassOverlimits."br0"."100".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassOverlimits."br0"."100".2 = INTEGER: 4029
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPackets."br0"."100" = INTEGER: 1248071
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPps."br0"."100" = INTEGER: 23749
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBytes."br0"."100" = INTEGER: 1877649441
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInDrops."br0"."100" = INTEGER: 6303
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInKind."br0"."100" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBps."br0"."100" = INTEGER: 35082874
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInOverlimits."br0"."100" = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInRate."br0"."100" = INTEGER: 0

Test Traffic Control OIDs On Bonding Interface

Description

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

Scenario

Step 1: Set the following configuration in DUT0 :

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

Step 2: Set the following configuration in DUT1 :

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

Step 3: Ping IP address 192.168.100.1 from DUT1:

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

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.529/0.529/0.529/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 38560 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   185 MBytes  1.55 Gbits/sec  689   24.0 KBytes
[  5]   1.00-2.00   sec   142 MBytes  1.19 Gbits/sec  522   25.5 KBytes
[  5]   2.00-3.00   sec   168 MBytes  1.41 Gbits/sec  627   33.9 KBytes
[  5]   3.00-4.00   sec   147 MBytes  1.23 Gbits/sec  537   32.5 KBytes
[  5]   4.00-5.00   sec   171 MBytes  1.44 Gbits/sec  580   32.5 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   813 MBytes  1.36 Gbits/sec  2955             sender
[  5]   0.00-5.00   sec   813 MBytes  1.36 Gbits/sec                  receiver

iperf Done.

Step 5: Initiate a bandwidth test from DUT1 to DUT0

admin@DUT0$ monitor test performance server port 4321
admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 4321 parallel 1
Expect this output in DUT1:
Connecting to host 192.168.100.1, port 4321
[  5] local 192.168.100.2 port 50386 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   176 MBytes  1.47 Gbits/sec  670   36.8 KBytes
[  5]   1.00-2.00   sec   181 MBytes  1.52 Gbits/sec  633   18.4 KBytes
[  5]   2.00-3.00   sec   212 MBytes  1.78 Gbits/sec  778   12.7 KBytes
[  5]   3.00-4.00   sec   173 MBytes  1.45 Gbits/sec  657   26.9 KBytes
[  5]   4.00-5.00   sec   161 MBytes  1.35 Gbits/sec  672   31.1 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   904 MBytes  1.52 Gbits/sec  3410             sender
[  5]   0.00-5.00   sec   903 MBytes  1.51 Gbits/sec                  receiver

iperf Done.

Step 6: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 1234
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 1234 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 1234
[  5] local 192.168.100.1 port 41840 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  13.8 MBytes   116 Mbits/sec  149   73.5 KBytes
[  5]   1.00-2.00   sec  11.3 MBytes  94.9 Mbits/sec   75   77.8 KBytes
[  5]   2.00-3.00   sec  11.7 MBytes  98.5 Mbits/sec   72   83.4 KBytes
[  5]   3.00-4.00   sec  11.3 MBytes  94.9 Mbits/sec   84   66.5 KBytes
[  5]   4.00-5.00   sec  11.3 MBytes  94.9 Mbits/sec   73   72.1 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.5 MBytes  99.8 Mbits/sec  453             sender
[  5]   0.00-5.00   sec  58.5 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

Step 7: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 4321
admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 4321 parallel 1
Expect this output in DUT0:
Connecting to host 192.168.100.2, port 4321
[  5] local 192.168.100.1 port 50104 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.1 MBytes   119 Mbits/sec  156   77.8 KBytes
[  5]   1.00-2.00   sec  11.4 MBytes  95.9 Mbits/sec   72   77.8 KBytes
[  5]   2.00-3.00   sec  11.3 MBytes  94.9 Mbits/sec   65   77.8 KBytes
[  5]   3.00-4.00   sec  11.2 MBytes  94.3 Mbits/sec   73   73.5 KBytes
[  5]   4.00-5.00   sec  11.4 MBytes  95.4 Mbits/sec   73   76.4 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.5 MBytes  99.8 Mbits/sec  439             sender
[  5]   0.00-5.00   sec  58.4 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

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

OutKind\.[^=]+ = STRING: (htb|ceetm)
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: \d+
OutRate\.[^=]+ = INTEGER: 100000000
InPps\.[^=]+ = INTEGER: [1-9]\d*
InDrops\.[^=]+ = INTEGER: [1-9]\d*
InOverlimits\.[^=]+ = INTEGER: \d+
InRate\.[^=]+ = INTEGER: 0
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPackets."bond0" = INTEGER: 269774
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPps."bond0" = INTEGER: 9460
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBytes."bond0" = INTEGER: 140755960
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutDrops."bond0" = INTEGER: 35
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutKind."bond0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBps."bond0" = INTEGER: 9411980
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutOverlimits."bond0" = INTEGER: 7895
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutRate."bond0" = INTEGER: 100000000
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassTag."bond0".1 = INTEGER: 1
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassTag."bond0".2 = INTEGER: 2
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassPackets."bond0".1 = INTEGER: 86831
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassPackets."bond0".2 = INTEGER: 182943
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".1 = INTEGER: 5841549
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".2 = INTEGER: 134914411
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassDrops."bond0".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassDrops."bond0".2 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassOverlimits."bond0".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassOverlimits."bond0".2 = INTEGER: 4155
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPackets."bond0" = INTEGER: 1251627
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPps."bond0" = INTEGER: 23495
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBytes."bond0" = INTEGER: 1881441282
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInDrops."bond0" = INTEGER: 6415
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInKind."bond0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBps."bond0" = INTEGER: 34636907
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInOverlimits."bond0" = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInRate."bond0" = INTEGER: 0

Test Traffic Control OIDs On Tunnel Interface

Description

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

Scenario

Step 1: Set the following configuration in DUT0 :

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

Step 2: Set the following configuration in DUT1 :

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

Step 3: Ping IP address 10.0.0.1 from DUT1:

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

--- 10.0.0.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.600/0.600/0.600/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 33426 connected to 10.0.0.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   281 MBytes  2.35 Gbits/sec  855    102 KBytes
[  5]   1.00-2.00   sec   269 MBytes  2.25 Gbits/sec  1139    346 KBytes
[  5]   2.00-3.00   sec   305 MBytes  2.56 Gbits/sec  1442   45.9 KBytes
[  5]   3.00-4.00   sec   274 MBytes  2.30 Gbits/sec  986   91.8 KBytes
[  5]   4.00-5.00   sec   272 MBytes  2.29 Gbits/sec  892   61.2 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.37 GBytes  2.35 Gbits/sec  5314             sender
[  5]   0.00-5.00   sec  1.36 GBytes  2.34 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 50338 connected to 10.0.0.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   263 MBytes  2.20 Gbits/sec  1075    191 KBytes
[  5]   1.00-2.00   sec   299 MBytes  2.51 Gbits/sec  1179   40.3 KBytes
[  5]   2.00-3.00   sec   321 MBytes  2.69 Gbits/sec  1319   68.1 KBytes
[  5]   3.00-4.00   sec   331 MBytes  2.78 Gbits/sec  1151   55.6 KBytes
[  5]   4.00-5.00   sec   251 MBytes  2.11 Gbits/sec  846    209 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.43 GBytes  2.46 Gbits/sec  5570             sender
[  5]   0.00-5.00   sec  1.43 GBytes  2.45 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 52616 connected to 10.0.0.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.6 MBytes   123 Mbits/sec  228   62.6 KBytes
[  5]   1.00-2.00   sec  11.0 MBytes  92.3 Mbits/sec   30   87.6 KBytes
[  5]   2.00-3.00   sec  11.6 MBytes  97.4 Mbits/sec   71   86.2 KBytes
[  5]   3.00-4.00   sec  11.6 MBytes  97.4 Mbits/sec   71   82.0 KBytes
[  5]   4.00-5.00   sec  11.6 MBytes  97.4 Mbits/sec   57   93.2 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  60.5 MBytes   101 Mbits/sec  457             sender
[  5]   0.00-5.00   sec  59.0 MBytes  98.9 Mbits/sec                  receiver

iperf Done.

Step 7: Initiate a bandwidth test from DUT0 to DUT1

admin@DUT1$ monitor test performance server port 4321
admin@DUT0$ monitor test performance client 10.0.0.2 duration 5 port 4321 parallel 1
Expect this output in DUT0:
Connecting to host 10.0.0.2, port 4321
[  5] local 10.0.0.1 port 32814 connected to 10.0.0.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.3 MBytes   120 Mbits/sec  173   84.8 KBytes
[  5]   1.00-2.00   sec  11.6 MBytes  97.4 Mbits/sec   68   94.6 KBytes
[  5]   2.00-3.00   sec  11.6 MBytes  97.4 Mbits/sec   70   72.3 KBytes
[  5]   3.00-4.00   sec  11.6 MBytes  97.4 Mbits/sec   33   82.0 KBytes
[  5]   4.00-5.00   sec  11.1 MBytes  93.3 Mbits/sec   75   84.8 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  60.3 MBytes   101 Mbits/sec  419             sender
[  5]   0.00-5.00   sec  59.0 MBytes  98.9 Mbits/sec                  receiver

iperf Done.

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

OutKind\.[^=]+ = STRING: (htb|ceetm)
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: \d+
OutRate\.[^=]+ = INTEGER: 100000000
InPps\.[^=]+ = INTEGER: [1-9]\d*
InDrops\.[^=]+ = INTEGER: [1-9]\d*
InOverlimits\.[^=]+ = INTEGER: \d+
InRate\.[^=]+ = INTEGER: 0
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutPackets."tun0" = INTEGER: 155676
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutPps."tun0" = INTEGER: 7348
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBytes."tun0" = INTEGER: 131979803
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutDrops."tun0" = INTEGER: 31
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutKind."tun0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBps."tun0" = INTEGER: 9201867
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutOverlimits."tun0" = INTEGER: 7405
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutRate."tun0" = INTEGER: 100000000
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassTag."tun0".1 = INTEGER: 1
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassTag."tun0".2 = INTEGER: 2
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassPackets."tun0".1 = INTEGER: 33363
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassPackets."tun0".2 = INTEGER: 122313
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".1 = INTEGER: 1756220
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".2 = INTEGER: 130223583
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassDrops."tun0".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassDrops."tun0".2 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassOverlimits."tun0".1 = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassOverlimits."tun0".2 = INTEGER: 3896
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPackets."tun0" = INTEGER: 2110307
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPps."tun0" = INTEGER: 35243
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBytes."tun0" = INTEGER: 3108342828
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInDrops."tun0" = INTEGER: 948
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInKind."tun0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBps."tun0" = INTEGER: 51559959
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInOverlimits."tun0" = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInRate."tun0" = INTEGER: 0