Tc Snmp Monitor

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

Test Traffic Control OIDs On Ethernet Interface

Description

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

Scenario

Step 1: Set the following configuration in DUT0 :

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

Step 2: Set the following configuration in DUT1 :

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

Step 3: Ping IP address 192.168.100.1 from DUT1:

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

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.706/0.706/0.706/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 39504 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  83.2 MBytes   698 Mbits/sec  313   29.7 KBytes
[  5]   1.00-2.00   sec   108 MBytes   907 Mbits/sec  372   29.7 KBytes
[  5]   2.00-3.00   sec   108 MBytes   908 Mbits/sec  383   38.2 KBytes
[  5]   3.00-4.00   sec  83.0 MBytes   696 Mbits/sec  336   41.0 KBytes
[  5]   4.00-5.01   sec  87.9 MBytes   729 Mbits/sec  300   21.2 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.01   sec   470 MBytes   788 Mbits/sec  1704             sender
[  5]   0.00-5.01   sec   469 MBytes   786 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 41082 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  87.4 MBytes   733 Mbits/sec  290   21.2 KBytes
[  5]   1.00-2.00   sec  81.1 MBytes   680 Mbits/sec  261   31.1 KBytes
[  5]   2.00-3.01   sec  56.8 MBytes   472 Mbits/sec  223   45.2 KBytes
[  5]   3.01-4.00   sec  83.3 MBytes   704 Mbits/sec  300   33.9 KBytes
[  5]   4.00-5.00   sec  86.7 MBytes   727 Mbits/sec  308   29.7 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   395 MBytes   663 Mbits/sec  1382             sender
[  5]   0.00-5.00   sec   395 MBytes   662 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 47820 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  132   90.5 KBytes
[  5]   1.00-2.00   sec  11.7 MBytes  98.5 Mbits/sec    7    122 KBytes
[  5]   2.00-3.00   sec  11.2 MBytes  93.8 Mbits/sec   14    120 KBytes
[  5]   3.00-4.00   sec  11.8 MBytes  99.0 Mbits/sec    9    113 KBytes
[  5]   4.00-5.00   sec  11.2 MBytes  93.8 Mbits/sec    8    117 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.8 MBytes   100 Mbits/sec  170             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 57622 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  15.0 MBytes   126 Mbits/sec  167   87.7 KBytes
[  5]   1.00-2.00   sec  11.6 MBytes  97.0 Mbits/sec    2    129 KBytes
[  5]   2.00-3.00   sec  11.5 MBytes  96.4 Mbits/sec   53   84.8 KBytes
[  5]   3.00-4.00   sec  11.4 MBytes  95.9 Mbits/sec    6   89.1 KBytes
[  5]   4.00-5.00   sec  10.8 MBytes  90.7 Mbits/sec    8   94.7 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  60.3 MBytes   101 Mbits/sec  236             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::telOSDxMonDBInterfacesEthernetTrafficControlOutPackets."eth0" = INTEGER: 167814
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutPps."eth0" = INTEGER: 7299
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBytes."eth0" = INTEGER: 133903600
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutDrops."eth0" = INTEGER: 24
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutKind."eth0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBps."eth0" = INTEGER: 8953863
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutOverlimits."eth0" = INTEGER: 7599
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: 48082
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassPackets."eth0".2 = INTEGER: 119732
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".1 = INTEGER: 3243014
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".2 = INTEGER: 130660586
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: 4067
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPackets."eth0" = INTEGER: 635926
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPps."eth0" = INTEGER: 12044
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBytes."eth0" = INTEGER: 948123525
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInDrops."eth0" = INTEGER: 3141
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInKind."eth0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBps."eth0" = INTEGER: 17233479
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.344 ms

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.344/0.344/0.344/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 57812 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   106 MBytes   892 Mbits/sec  388   22.6 KBytes
[  5]   1.00-2.00   sec   114 MBytes   960 Mbits/sec  414   31.1 KBytes
[  5]   2.00-3.00   sec   142 MBytes  1.19 Gbits/sec  531   36.8 KBytes
[  5]   3.00-4.00   sec   127 MBytes  1.07 Gbits/sec  483   32.5 KBytes
[  5]   4.00-5.00   sec   127 MBytes  1.07 Gbits/sec  479   65.0 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   617 MBytes  1.03 Gbits/sec  2295             sender
[  5]   0.00-5.00   sec   616 MBytes  1.03 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 39740 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  96.0 MBytes   805 Mbits/sec  338   21.2 KBytes
[  5]   1.00-2.00   sec   116 MBytes   972 Mbits/sec  445   33.9 KBytes
[  5]   2.00-3.00   sec  92.4 MBytes   775 Mbits/sec  298   1.41 KBytes
[  5]   3.00-4.00   sec   136 MBytes  1.14 Gbits/sec  490   33.9 KBytes
[  5]   4.00-5.00   sec   151 MBytes  1.27 Gbits/sec  583   28.3 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   591 MBytes   992 Mbits/sec  2154             sender
[  5]   0.00-5.00   sec   591 MBytes   991 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 46076 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  15.3 MBytes   128 Mbits/sec  204   80.6 KBytes
[  5]   1.00-2.00   sec  10.9 MBytes  91.7 Mbits/sec    2   84.8 KBytes
[  5]   2.00-3.00   sec  12.0 MBytes   101 Mbits/sec   11   87.7 KBytes
[  5]   3.00-4.00   sec  10.9 MBytes  91.7 Mbits/sec    8   90.5 KBytes
[  5]   4.00-5.00   sec  11.9 MBytes   100 Mbits/sec    5   89.1 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  61.1 MBytes   102 Mbits/sec  230             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 43648 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.0 MBytes   118 Mbits/sec   81   83.4 KBytes
[  5]   1.00-2.00   sec  11.4 MBytes  95.9 Mbits/sec    0   96.2 KBytes
[  5]   2.00-3.00   sec  11.4 MBytes  95.9 Mbits/sec   11   96.2 KBytes
[  5]   3.00-4.00   sec  11.4 MBytes  95.4 Mbits/sec   42   82.0 KBytes
[  5]   4.00-5.00   sec  11.1 MBytes  92.8 Mbits/sec    8   94.7 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.3 MBytes  99.5 Mbits/sec  142             sender
[  5]   0.00-5.00   sec  58.5 MBytes  98.0 Mbits/sec                  receiver

iperf Done.

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

OutKind\.[^=]+ = STRING: (htb|ceetm)
OutPackets\.[^=]+ = INTEGER: [1-9]\d*
OutBytes\.[^=]+ = INTEGER: [1-9]\d*
InKind\.[^=]+ = STRING: netem
InPackets\.[^=]+ = INTEGER: [1-9]\d*
InBytes\.[^=]+ = INTEGER: [1-9]\d*
OutDrops\.[^=]+ = INTEGER: \d+
OutOverlimits\.[^=]+ = INTEGER: \d+
OutRate\.[^=]+ = INTEGER: 100000000
InPps\.[^=]+ = INTEGER: [1-9]\d*
InDrops\.[^=]+ = INTEGER: [1-9]\d*
InOverlimits\.[^=]+ = INTEGER: \d+
InRate\.[^=]+ = INTEGER: 0
OutClassPackets\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassPackets\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.1 = INTEGER: [1-9]\d*
OutClassBytes\.[^=]+\.2 = INTEGER: [1-9]\d*
OutClassDrops\.[^=]+\.1 = INTEGER: \d+
OutClassDrops\.[^=]+\.2 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.1 = INTEGER: \d+
OutClassOverlimits\.[^=]+\.2 = INTEGER: \d+
OutPps\.[^=]+ = INTEGER: [1-9]\d*
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutPackets."eth0"."100" = INTEGER: 209897
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutPps."eth0"."100" = INTEGER: 8349
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBytes."eth0"."100" = INTEGER: 136711342
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutDrops."eth0"."100" = INTEGER: 22
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutKind."eth0"."100" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBps."eth0"."100" = INTEGER: 9081430
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutOverlimits."eth0"."100" = INTEGER: 8243
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: 58113
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassPackets."eth0"."100".2 = INTEGER: 151784
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".1 = INTEGER: 3923231
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".2 = INTEGER: 132788111
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: 4399
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPackets."eth0"."100" = INTEGER: 884452
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPps."eth0"."100" = INTEGER: 17340
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBytes."eth0"."100" = INTEGER: 1323992038
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInDrops."eth0"."100" = INTEGER: 4489
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInKind."eth0"."100" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBps."eth0"."100" = INTEGER: 25248849
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.458 ms

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.458/0.458/0.458/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 44802 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   129 MBytes  1.08 Gbits/sec  489   18.4 KBytes
[  5]   1.00-2.00   sec   125 MBytes  1.04 Gbits/sec  454   36.8 KBytes
[  5]   2.00-3.00   sec   138 MBytes  1.16 Gbits/sec  522   28.3 KBytes
[  5]   3.00-4.00   sec   102 MBytes   854 Mbits/sec  353   33.9 KBytes
[  5]   4.00-5.00   sec   115 MBytes   964 Mbits/sec  424   32.5 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   609 MBytes  1.02 Gbits/sec  2242             sender
[  5]   0.00-5.00   sec   608 MBytes  1.02 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 58946 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   163 MBytes  1.37 Gbits/sec  576   19.8 KBytes
[  5]   1.00-2.00   sec   148 MBytes  1.24 Gbits/sec  569   36.8 KBytes
[  5]   2.00-3.00   sec  68.0 MBytes   571 Mbits/sec  245   21.2 KBytes
[  5]   3.00-4.00   sec  37.4 MBytes   314 Mbits/sec  153   1.41 KBytes
[  5]   4.00-5.00   sec  81.2 MBytes   681 Mbits/sec  277   15.6 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   498 MBytes   835 Mbits/sec  1820             sender
[  5]   0.00-5.00   sec   497 MBytes   834 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 57100 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  16.6 MBytes   139 Mbits/sec  255    100 KBytes
[  5]   1.00-2.00   sec  11.2 MBytes  94.4 Mbits/sec    9   96.2 KBytes
[  5]   2.00-3.00   sec  11.2 MBytes  94.4 Mbits/sec    8   99.0 KBytes
[  5]   3.00-4.00   sec  11.2 MBytes  94.4 Mbits/sec    6   99.0 KBytes
[  5]   4.00-5.00   sec  11.2 MBytes  94.4 Mbits/sec    3    136 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  61.6 MBytes   103 Mbits/sec  281             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 41634 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.4 MBytes   120 Mbits/sec  109    126 KBytes
[  5]   1.00-2.00   sec  11.4 MBytes  95.9 Mbits/sec   57   90.5 KBytes
[  5]   2.00-3.00   sec  11.7 MBytes  98.0 Mbits/sec   45    122 KBytes
[  5]   3.00-4.00   sec  11.1 MBytes  92.8 Mbits/sec    5    122 KBytes
[  5]   4.00-5.00   sec  11.9 MBytes  99.6 Mbits/sec    9    119 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  60.4 MBytes   101 Mbits/sec  225             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: 206985
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutPps."br0" = INTEGER: 8081
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBytes."br0" = INTEGER: 136583095
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutDrops."br0" = INTEGER: 25
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutKind."br0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBps."br0" = INTEGER: 9309115
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutOverlimits."br0" = INTEGER: 7388
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: 65513
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassPackets."br0".2 = INTEGER: 141472
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".1 = INTEGER: 4409647
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".2 = INTEGER: 132173448
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: 3965
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPackets."br0" = INTEGER: 811693
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPps."br0" = INTEGER: 14078
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBytes."br0" = INTEGER: 1212474936
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInDrops."br0" = INTEGER: 4108
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInKind."br0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBps."br0" = INTEGER: 20208032
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.244 ms

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.244/0.244/0.244/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 56114 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   107 MBytes   896 Mbits/sec  360   25.5 KBytes
[  5]   1.00-2.00   sec   104 MBytes   875 Mbits/sec  380   22.6 KBytes
[  5]   2.00-3.00   sec   111 MBytes   927 Mbits/sec  407   19.8 KBytes
[  5]   3.00-4.00   sec   113 MBytes   946 Mbits/sec  414   15.6 KBytes
[  5]   4.00-5.00   sec  91.8 MBytes   770 Mbits/sec  349   19.8 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   526 MBytes   883 Mbits/sec  1910             sender
[  5]   0.00-5.00   sec   526 MBytes   882 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 37616 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  71.3 MBytes   598 Mbits/sec  238   33.9 KBytes
[  5]   1.00-2.00   sec   133 MBytes  1.11 Gbits/sec  472   31.1 KBytes
[  5]   2.00-3.00   sec   132 MBytes  1.11 Gbits/sec  520   32.5 KBytes
[  5]   3.00-4.00   sec   145 MBytes  1.21 Gbits/sec  546   28.3 KBytes
[  5]   4.00-5.00   sec  98.1 MBytes   823 Mbits/sec  366   17.0 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   579 MBytes   972 Mbits/sec  2142             sender
[  5]   0.00-5.00   sec   579 MBytes   971 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 53682 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.01   sec  14.0 MBytes   116 Mbits/sec   83    132 KBytes
[  5]   1.01-2.00   sec  11.4 MBytes  96.7 Mbits/sec   60    112 KBytes
[  5]   2.00-3.00   sec  11.3 MBytes  94.9 Mbits/sec    6    112 KBytes
[  5]   3.00-4.00   sec  11.8 MBytes  99.0 Mbits/sec   15    123 KBytes
[  5]   4.00-5.00   sec  11.2 MBytes  94.4 Mbits/sec   19    110 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.8 MBytes   100 Mbits/sec  183             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 42252 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   98    103 KBytes
[  5]   1.00-2.00   sec  11.2 MBytes  94.4 Mbits/sec    5    100 KBytes
[  5]   2.00-3.00   sec  11.7 MBytes  98.5 Mbits/sec    7    103 KBytes
[  5]   3.00-4.00   sec  11.2 MBytes  93.8 Mbits/sec    5    106 KBytes
[  5]   4.00-5.00   sec  11.7 MBytes  98.5 Mbits/sec    7    102 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  60.0 MBytes   101 Mbits/sec  122             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: 185025
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutPps."br0"."100" = INTEGER: 7842
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBytes."br0"."100" = INTEGER: 135070813
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutDrops."br0"."100" = INTEGER: 23
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutKind."br0"."100" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBps."br0"."100" = INTEGER: 9081597
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutOverlimits."br0"."100" = INTEGER: 7370
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: 46902
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassPackets."br0"."100".2 = INTEGER: 138123
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".1 = INTEGER: 3171621
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".2 = INTEGER: 131899192
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: 3950
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPackets."br0"."100" = INTEGER: 809984
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPps."br0"."100" = INTEGER: 16014
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBytes."br0"."100" = INTEGER: 1211870512
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInDrops."br0"."100" = INTEGER: 4106
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInKind."br0"."100" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBps."br0"."100" = INTEGER: 23222061
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.595 ms

--- 192.168.100.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.595/0.595/0.595/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 57810 connected to 192.168.100.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  83.8 MBytes   702 Mbits/sec  317   31.1 KBytes
[  5]   1.00-2.00   sec  83.3 MBytes   699 Mbits/sec  307   46.7 KBytes
[  5]   2.00-3.00   sec  83.6 MBytes   701 Mbits/sec  293   15.6 KBytes
[  5]   3.00-4.00   sec  74.0 MBytes   621 Mbits/sec  308   17.0 KBytes
[  5]   4.00-5.00   sec   114 MBytes   953 Mbits/sec  402   25.5 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   438 MBytes   735 Mbits/sec  1627             sender
[  5]   0.00-5.00   sec   438 MBytes   734 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 56386 connected to 192.168.100.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   139 MBytes  1.17 Gbits/sec  475   24.0 KBytes
[  5]   1.00-2.00   sec   122 MBytes  1.02 Gbits/sec  419   36.8 KBytes
[  5]   2.00-3.00   sec   109 MBytes   915 Mbits/sec  401   22.6 KBytes
[  5]   3.00-4.00   sec   149 MBytes  1.25 Gbits/sec  577   38.2 KBytes
[  5]   4.00-5.00   sec   155 MBytes  1.30 Gbits/sec  534   45.2 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec   673 MBytes  1.13 Gbits/sec  2406             sender
[  5]   0.00-5.00   sec   671 MBytes  1.13 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 58250 connected to 192.168.100.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  15.3 MBytes   128 Mbits/sec  156    117 KBytes
[  5]   1.00-2.00   sec  10.9 MBytes  91.7 Mbits/sec   30    109 KBytes
[  5]   2.00-3.00   sec  12.0 MBytes   101 Mbits/sec   11    134 KBytes
[  5]   3.00-4.00   sec  10.9 MBytes  91.7 Mbits/sec   23   84.8 KBytes
[  5]   4.00-5.00   sec  11.9 MBytes   100 Mbits/sec    7    119 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  61.1 MBytes   102 Mbits/sec  227             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 53298 connected to 192.168.100.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  13.9 MBytes   117 Mbits/sec   64   97.6 KBytes
[  5]   1.00-2.00   sec  11.7 MBytes  98.0 Mbits/sec    3    134 KBytes
[  5]   2.00-3.00   sec  11.2 MBytes  93.8 Mbits/sec   15   91.9 KBytes
[  5]   3.00-4.00   sec  11.7 MBytes  98.0 Mbits/sec    3    132 KBytes
[  5]   4.00-5.00   sec  11.1 MBytes  92.8 Mbits/sec   26   83.4 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  59.5 MBytes  99.9 Mbits/sec  111             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
Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPackets."bond0" = INTEGER: 197955
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPps."bond0" = INTEGER: 8276
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBytes."bond0" = INTEGER: 135951140
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutDrops."bond0" = INTEGER: 24
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutKind."bond0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBps."bond0" = INTEGER: 9083490
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutOverlimits."bond0" = INTEGER: 7383
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: 46136
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassPackets."bond0".2 = INTEGER: 151819
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".1 = INTEGER: 3110164
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".2 = INTEGER: 132840976
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: 3930
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPackets."bond0" = INTEGER: 813331
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPps."bond0" = INTEGER: 17657
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBytes."bond0" = INTEGER: 1216566093
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInDrops."bond0" = INTEGER: 4086
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInKind."bond0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBps."bond0" = INTEGER: 25665125
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.450 ms

--- 10.0.0.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.450/0.450/0.450/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 55328 connected to 10.0.0.1 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   206 MBytes  1.72 Gbits/sec  678   77.9 KBytes
[  5]   1.00-2.00   sec   230 MBytes  1.93 Gbits/sec  864   76.5 KBytes
[  5]   2.00-3.00   sec   201 MBytes  1.69 Gbits/sec  825   55.6 KBytes
[  5]   3.00-4.00   sec   226 MBytes  1.90 Gbits/sec  775   54.2 KBytes
[  5]   4.00-5.00   sec   212 MBytes  1.78 Gbits/sec  749   91.8 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.05 GBytes  1.80 Gbits/sec  3891             sender
[  5]   0.00-5.00   sec  1.05 GBytes  1.80 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 46010 connected to 10.0.0.1 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   197 MBytes  1.66 Gbits/sec  780    118 KBytes
[  5]   1.00-2.00   sec   246 MBytes  2.07 Gbits/sec  868   55.6 KBytes
[  5]   2.00-3.00   sec   277 MBytes  2.32 Gbits/sec  991   52.8 KBytes
[  5]   3.00-4.00   sec   286 MBytes  2.40 Gbits/sec  1170   43.1 KBytes
[  5]   4.00-5.00   sec   246 MBytes  2.07 Gbits/sec  900    234 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  1.22 GBytes  2.10 Gbits/sec  4709             sender
[  5]   0.00-5.00   sec  1.22 GBytes  2.10 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 45208 connected to 10.0.0.2 port 1234
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  14.3 MBytes   120 Mbits/sec   94   94.6 KBytes
[  5]   1.00-2.00   sec  11.2 MBytes  94.3 Mbits/sec   11   90.4 KBytes
[  5]   2.00-3.00   sec  11.7 MBytes  98.4 Mbits/sec    4    132 KBytes
[  5]   3.00-4.00   sec  11.2 MBytes  94.3 Mbits/sec   52   94.6 KBytes
[  5]   4.00-5.00   sec  11.8 MBytes  98.9 Mbits/sec    8    135 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  60.3 MBytes   101 Mbits/sec  169             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 59704 connected to 10.0.0.2 port 4321
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  13.9 MBytes   117 Mbits/sec   64    140 KBytes
[  5]   1.00-2.00   sec  11.6 MBytes  96.9 Mbits/sec   38    134 KBytes
[  5]   2.00-3.00   sec  11.6 MBytes  96.9 Mbits/sec   83   94.6 KBytes
[  5]   3.00-4.00   sec  11.6 MBytes  96.9 Mbits/sec   19    118 KBytes
[  5]   4.00-5.00   sec  11.6 MBytes  96.9 Mbits/sec   50   93.2 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-5.00   sec  60.1 MBytes   101 Mbits/sec  254             sender
[  5]   0.00-5.00   sec  58.9 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: 167994
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutPps."tun0" = INTEGER: 7632
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBytes."tun0" = INTEGER: 132565996
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutDrops."tun0" = INTEGER: 21
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutKind."tun0" = STRING: htb
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBps."tun0" = INTEGER: 9210228
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutOverlimits."tun0" = INTEGER: 7579
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: 38500
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassPackets."tun0".2 = INTEGER: 129494
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".1 = INTEGER: 2023331
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".2 = INTEGER: 130542665
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: 4065
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPackets."tun0" = INTEGER: 1717741
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPps."tun0" = INTEGER: 31399
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBytes."tun0" = INTEGER: 2525654586
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInDrops."tun0" = INTEGER: 936
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInKind."tun0" = STRING: netem
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBps."tun0" = INTEGER: 45661431
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInOverlimits."tun0" = INTEGER: 0
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInRate."tun0" = INTEGER: 0