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 1Show 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.752 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.752/0.752/0.752/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 1Expect this output in
DUT1:Connecting to host 192.168.100.1, port 1234 [ 5] local 192.168.100.2 port 32990 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 75.2 MBytes 631 Mbits/sec 269 33.9 KBytes [ 5] 1.00-2.00 sec 90.9 MBytes 763 Mbits/sec 334 35.4 KBytes [ 5] 2.00-3.00 sec 93.5 MBytes 785 Mbits/sec 322 21.2 KBytes [ 5] 3.00-4.00 sec 57.5 MBytes 482 Mbits/sec 206 42.4 KBytes [ 5] 4.00-5.00 sec 139 MBytes 1.16 Gbits/sec 520 53.7 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 456 MBytes 765 Mbits/sec 1651 sender [ 5] 0.00-5.01 sec 455 MBytes 763 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 1Expect this output in
DUT1:Connecting to host 192.168.100.1, port 4321 [ 5] local 192.168.100.2 port 36764 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 190 MBytes 1.60 Gbits/sec 687 35.4 KBytes [ 5] 1.00-2.00 sec 164 MBytes 1.38 Gbits/sec 591 28.3 KBytes [ 5] 2.00-3.00 sec 153 MBytes 1.29 Gbits/sec 570 32.5 KBytes [ 5] 3.00-4.00 sec 137 MBytes 1.15 Gbits/sec 479 19.8 KBytes [ 5] 4.00-5.00 sec 122 MBytes 1.02 Gbits/sec 440 62.2 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 767 MBytes 1.29 Gbits/sec 2767 sender [ 5] 0.00-5.00 sec 767 MBytes 1.29 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 1Expect this output in
DUT0:Connecting to host 192.168.100.2, port 1234 [ 5] local 192.168.100.1 port 55178 connected to 192.168.100.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.3 MBytes 120 Mbits/sec 92 94.7 KBytes [ 5] 1.00-2.00 sec 11.3 MBytes 94.9 Mbits/sec 13 93.3 KBytes [ 5] 2.00-3.00 sec 11.2 MBytes 93.8 Mbits/sec 4 136 KBytes [ 5] 3.00-4.00 sec 11.7 MBytes 98.5 Mbits/sec 12 89.1 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 94.4 Mbits/sec 6 91.9 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.8 MBytes 100 Mbits/sec 127 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 1Expect this output in
DUT0:Connecting to host 192.168.100.2, port 4321 [ 5] local 192.168.100.1 port 57526 connected to 192.168.100.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 15.2 MBytes 128 Mbits/sec 196 94.7 KBytes [ 5] 1.00-2.00 sec 11.7 MBytes 98.5 Mbits/sec 32 132 KBytes [ 5] 2.00-3.00 sec 11.7 MBytes 98.0 Mbits/sec 18 119 KBytes [ 5] 3.00-4.00 sec 11.7 MBytes 98.0 Mbits/sec 46 106 KBytes [ 5] 4.00-5.00 sec 10.5 MBytes 88.3 Mbits/sec 7 134 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 60.9 MBytes 102 Mbits/sec 299 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: 235066 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutPps."eth0" = INTEGER: 8885 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBytes."eth0" = INTEGER: 138408741 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: 9158009 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutOverlimits."eth0" = INTEGER: 7420 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: 55771 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassPackets."eth0".2 = INTEGER: 179295 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".1 = INTEGER: 3746977 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".2 = INTEGER: 134661764 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: 3970 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPackets."eth0" = INTEGER: 897370 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPps."eth0" = INTEGER: 18611 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBytes."eth0" = INTEGER: 1340470042 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInDrops."eth0" = INTEGER: 4493 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInKind."eth0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBps."eth0" = INTEGER: 26942905 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 1Show 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.487 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.487/0.487/0.487/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 1Expect this output in
DUT1:Connecting to host 192.168.100.1, port 1234 [ 5] local 192.168.100.2 port 43936 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 112 MBytes 936 Mbits/sec 394 31.1 KBytes [ 5] 1.00-2.00 sec 105 MBytes 883 Mbits/sec 367 24.0 KBytes [ 5] 2.00-3.00 sec 118 MBytes 986 Mbits/sec 442 31.1 KBytes [ 5] 3.00-4.00 sec 138 MBytes 1.15 Gbits/sec 489 32.5 KBytes [ 5] 4.00-5.00 sec 153 MBytes 1.28 Gbits/sec 632 50.9 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 625 MBytes 1.05 Gbits/sec 2324 sender [ 5] 0.00-5.00 sec 624 MBytes 1.05 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 1Expect this output in
DUT1:Connecting to host 192.168.100.1, port 4321 [ 5] local 192.168.100.2 port 45724 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 209 MBytes 1.75 Gbits/sec 736 46.7 KBytes [ 5] 1.00-2.00 sec 197 MBytes 1.65 Gbits/sec 747 28.3 KBytes [ 5] 2.00-3.00 sec 163 MBytes 1.37 Gbits/sec 607 55.1 KBytes [ 5] 3.00-4.00 sec 198 MBytes 1.66 Gbits/sec 709 29.7 KBytes [ 5] 4.00-5.00 sec 184 MBytes 1.54 Gbits/sec 671 35.4 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 951 MBytes 1.59 Gbits/sec 3470 sender [ 5] 0.00-5.00 sec 950 MBytes 1.59 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 1Expect this output in
DUT0:Connecting to host 192.168.100.2, port 1234 [ 5] local 192.168.100.1 port 58020 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 100 96.2 KBytes [ 5] 1.00-2.00 sec 11.7 MBytes 98.5 Mbits/sec 48 96.2 KBytes [ 5] 2.00-3.00 sec 11.2 MBytes 93.8 Mbits/sec 14 106 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 93.8 Mbits/sec 12 99.0 KBytes [ 5] 4.00-5.00 sec 11.7 MBytes 98.5 Mbits/sec 4 137 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.8 MBytes 100 Mbits/sec 178 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 1Expect this output in
DUT0:Connecting to host 192.168.100.2, port 4321 [ 5] local 192.168.100.1 port 43958 connected to 192.168.100.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.4 MBytes 121 Mbits/sec 111 115 KBytes [ 5] 1.00-2.00 sec 11.6 MBytes 97.0 Mbits/sec 37 109 KBytes [ 5] 2.00-3.00 sec 11.3 MBytes 94.9 Mbits/sec 49 99.0 KBytes [ 5] 3.00-4.00 sec 11.5 MBytes 96.4 Mbits/sec 18 110 KBytes [ 5] 4.00-5.00 sec 11.4 MBytes 95.4 Mbits/sec 31 84.8 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 60.1 MBytes 101 Mbits/sec 246 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: 264387 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutPps."eth0"."100" = INTEGER: 9608 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBytes."eth0"."100" = INTEGER: 140431182 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutDrops."eth0"."100" = INTEGER: 24 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutKind."eth0"."100" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBps."eth0"."100" = INTEGER: 9370862 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutOverlimits."eth0"."100" = INTEGER: 7537 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: 67189 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassPackets."eth0"."100".2 = INTEGER: 197198 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".1 = INTEGER: 4524890 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".2 = INTEGER: 135906292 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: 4032 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPackets."eth0"."100" = INTEGER: 1150107 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPps."eth0"."100" = INTEGER: 22970 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBytes."eth0"."100" = INTEGER: 1726574606 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInDrops."eth0"."100" = INTEGER: 5849 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInKind."eth0"."100" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBps."eth0"."100" = INTEGER: 33791110 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 1Show 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.438 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.438/0.438/0.438/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 1Expect this output in
DUT1:Connecting to host 192.168.100.1, port 1234 [ 5] local 192.168.100.2 port 40554 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 137 MBytes 1.15 Gbits/sec 504 25.5 KBytes [ 5] 1.00-2.00 sec 67.0 MBytes 562 Mbits/sec 241 35.4 KBytes [ 5] 2.00-3.00 sec 0.00 Bytes 0.00 bits/sec 2 1.41 KBytes [ 5] 3.00-4.00 sec 0.00 Bytes 0.00 bits/sec 1 1.41 KBytes [ 5] 4.00-5.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 204 MBytes 343 Mbits/sec 748 sender [ 5] 0.00-5.02 sec 204 MBytes 341 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 1Expect this output in
DUT1:Connecting to host 192.168.100.1, port 4321 [ 5] local 192.168.100.2 port 57056 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 32.8 MBytes 275 Mbits/sec 118 33.9 KBytes [ 5] 1.00-2.00 sec 31.7 MBytes 266 Mbits/sec 115 11.3 KBytes [ 5] 2.00-3.00 sec 84.7 MBytes 711 Mbits/sec 318 28.3 KBytes [ 5] 3.00-4.00 sec 129 MBytes 1.08 Gbits/sec 449 25.5 KBytes [ 5] 4.00-5.00 sec 184 MBytes 1.54 Gbits/sec 667 56.6 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 462 MBytes 775 Mbits/sec 1667 sender [ 5] 0.00-5.00 sec 460 MBytes 772 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 1Expect this output in
DUT0:Connecting to host 192.168.100.2, port 1234 [ 5] local 192.168.100.1 port 34048 connected to 192.168.100.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.1 MBytes 118 Mbits/sec 64 94.7 KBytes [ 5] 1.00-2.00 sec 11.4 MBytes 95.9 Mbits/sec 1 134 KBytes [ 5] 2.00-3.00 sec 11.4 MBytes 95.9 Mbits/sec 11 90.5 KBytes [ 5] 3.00-4.00 sec 11.4 MBytes 95.9 Mbits/sec 9 124 KBytes [ 5] 4.00-5.00 sec 11.4 MBytes 95.9 Mbits/sec 15 84.8 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.8 MBytes 100 Mbits/sec 100 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 1Expect this output in
DUT0:Connecting to host 192.168.100.2, port 4321 [ 5] local 192.168.100.1 port 42496 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 84 109 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 93.8 Mbits/sec 4 109 KBytes [ 5] 2.00-3.00 sec 11.5 MBytes 96.4 Mbits/sec 38 100 KBytes [ 5] 3.00-4.00 sec 11.4 MBytes 95.4 Mbits/sec 20 100 KBytes [ 5] 4.00-5.00 sec 11.5 MBytes 96.4 Mbits/sec 4 96.2 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.6 MBytes 99.9 Mbits/sec 150 sender [ 5] 0.00-5.00 sec 58.4 MBytes 98.0 Mbits/sec receiver iperf Done.
Step 8: Run command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl at DUT0 and check if output matches the following regular expressions:
OutKind\.[^=]+ = STRING: (htb|ceetm) OutPackets\.[^=]+ = INTEGER: [1-9]\d* OutBytes\.[^=]+ = INTEGER: [1-9]\d* InKind\.[^=]+ = STRING: netem InPackets\.[^=]+ = INTEGER: [1-9]\d* InBytes\.[^=]+ = INTEGER: [1-9]\d* OutDrops\.[^=]+ = INTEGER: \d+ OutOverlimits\.[^=]+ = INTEGER: \d+ OutRate\.[^=]+ = INTEGER: 100000000 InPps\.[^=]+ = INTEGER: [1-9]\d* InDrops\.[^=]+ = INTEGER: [1-9]\d* InOverlimits\.[^=]+ = INTEGER: \d+ InRate\.[^=]+ = INTEGER: 0 OutClassPackets\.[^=]+\.1 = INTEGER: [1-9]\d* OutClassPackets\.[^=]+\.2 = INTEGER: [1-9]\d* OutClassBytes\.[^=]+\.1 = INTEGER: [1-9]\d* OutClassBytes\.[^=]+\.2 = INTEGER: [1-9]\d* OutClassDrops\.[^=]+\.1 = INTEGER: \d+ OutClassDrops\.[^=]+\.2 = INTEGER: \d+ OutClassOverlimits\.[^=]+\.1 = INTEGER: \d+ OutClassOverlimits\.[^=]+\.2 = INTEGER: \d+ OutPps\.[^=]+ = INTEGER: [1-9]\d*Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutPackets."br0" = INTEGER: 167074 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutPps."br0" = INTEGER: 7786 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBytes."br0" = INTEGER: 133775271 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutDrops."br0" = INTEGER: 23 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutKind."br0" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBps."br0" = INTEGER: 9321723 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutOverlimits."br0" = INTEGER: 7534 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: 26280 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassPackets."br0".2 = INTEGER: 140794 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".1 = INTEGER: 1764535 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".2 = INTEGER: 132010736 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: 4027 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPackets."br0" = INTEGER: 492342 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPps."br0" = INTEGER: 10895 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBytes."br0" = INTEGER: 729054780 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInDrops."br0" = INTEGER: 2461 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInKind."br0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBps."br0" = INTEGER: 15393931 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 1Show 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.402 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.402/0.402/0.402/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 1Expect this output in
DUT1:Connecting to host 192.168.100.1, port 1234 [ 5] local 192.168.100.2 port 37866 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 87.2 MBytes 732 Mbits/sec 323 31.1 KBytes [ 5] 1.00-2.00 sec 101 MBytes 843 Mbits/sec 374 45.2 KBytes [ 5] 2.00-3.00 sec 79.3 MBytes 666 Mbits/sec 315 31.1 KBytes [ 5] 3.00-4.00 sec 101 MBytes 850 Mbits/sec 335 21.2 KBytes [ 5] 4.00-5.00 sec 140 MBytes 1.17 Gbits/sec 518 24.0 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 508 MBytes 853 Mbits/sec 1865 sender [ 5] 0.00-5.00 sec 508 MBytes 852 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 1Expect this output in
DUT1:Connecting to host 192.168.100.1, port 4321 [ 5] local 192.168.100.2 port 35390 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 155 MBytes 1.30 Gbits/sec 606 33.9 KBytes [ 5] 1.00-2.00 sec 188 MBytes 1.57 Gbits/sec 701 28.3 KBytes [ 5] 2.00-3.00 sec 224 MBytes 1.88 Gbits/sec 815 79.2 KBytes [ 5] 3.00-4.00 sec 218 MBytes 1.83 Gbits/sec 784 31.1 KBytes [ 5] 4.00-5.00 sec 201 MBytes 1.69 Gbits/sec 734 38.2 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 987 MBytes 1.66 Gbits/sec 3640 sender [ 5] 0.00-5.00 sec 986 MBytes 1.65 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 1Expect this output in
DUT0:Connecting to host 192.168.100.2, port 1234 [ 5] local 192.168.100.1 port 58902 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 68 97.6 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 93.8 Mbits/sec 2 134 KBytes [ 5] 2.00-3.00 sec 11.6 MBytes 97.5 Mbits/sec 14 96.2 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 93.8 Mbits/sec 57 97.6 KBytes [ 5] 4.00-5.00 sec 11.7 MBytes 98.0 Mbits/sec 9 102 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.9 MBytes 100 Mbits/sec 150 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 1Expect this output in
DUT0:Connecting to host 192.168.100.2, port 4321 [ 5] local 192.168.100.1 port 43078 connected to 192.168.100.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 13.8 MBytes 115 Mbits/sec 83 86.3 KBytes [ 5] 1.00-2.00 sec 11.4 MBytes 95.9 Mbits/sec 8 122 KBytes [ 5] 2.00-3.00 sec 11.5 MBytes 96.4 Mbits/sec 8 87.7 KBytes [ 5] 3.00-4.00 sec 11.4 MBytes 95.9 Mbits/sec 5 87.7 KBytes [ 5] 4.00-5.00 sec 11.5 MBytes 96.4 Mbits/sec 6 86.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.6 MBytes 100 Mbits/sec 110 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: 242888 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutPps."br0"."100" = INTEGER: 9259 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBytes."br0"."100" = INTEGER: 138961642 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutDrops."br0"."100" = INTEGER: 24 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutKind."br0"."100" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBps."br0"."100" = INTEGER: 9394697 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutOverlimits."br0"."100" = INTEGER: 7583 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: 54046 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassPackets."br0"."100".2 = INTEGER: 188842 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".1 = INTEGER: 3637816 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".2 = INTEGER: 135323826 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: 4090 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPackets."br0"."100" = INTEGER: 1092899 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPps."br0"."100" = INTEGER: 22918 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBytes."br0"."100" = INTEGER: 1638549880 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInDrops."br0"."100" = INTEGER: 5571 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInKind."br0"."100" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBps."br0"."100" = INTEGER: 33559776 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 1Show 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.682 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.682/0.682/0.682/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 1Expect this output in
DUT1:Connecting to host 192.168.100.1, port 1234 [ 5] local 192.168.100.2 port 37600 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 85.4 MBytes 717 Mbits/sec 313 28.3 KBytes [ 5] 1.00-2.00 sec 81.2 MBytes 681 Mbits/sec 291 39.6 KBytes [ 5] 2.00-3.00 sec 113 MBytes 951 Mbits/sec 425 28.3 KBytes [ 5] 3.00-4.00 sec 125 MBytes 1.05 Gbits/sec 474 33.9 KBytes [ 5] 4.00-5.00 sec 4.04 MBytes 33.9 Mbits/sec 11 1.41 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 409 MBytes 687 Mbits/sec 1514 sender [ 5] 0.00-8.59 sec 409 MBytes 399 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 1Expect this output in
DUT1:Connecting to host 192.168.100.1, port 4321 [ 5] local 192.168.100.2 port 36632 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 81.3 MBytes 682 Mbits/sec 299 28.3 KBytes [ 5] 1.00-2.00 sec 106 MBytes 890 Mbits/sec 347 36.8 KBytes [ 5] 2.00-3.00 sec 136 MBytes 1.14 Gbits/sec 513 43.8 KBytes [ 5] 3.00-4.00 sec 219 MBytes 1.84 Gbits/sec 787 26.9 KBytes [ 5] 4.00-5.00 sec 212 MBytes 1.78 Gbits/sec 744 21.2 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 755 MBytes 1.27 Gbits/sec 2690 sender [ 5] 0.00-5.00 sec 754 MBytes 1.27 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 1Expect this output in
DUT0:Connecting to host 192.168.100.2, port 1234 [ 5] local 192.168.100.1 port 59698 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 77 119 KBytes [ 5] 1.00-2.00 sec 11.4 MBytes 95.9 Mbits/sec 11 83.4 KBytes [ 5] 2.00-3.00 sec 11.5 MBytes 96.4 Mbits/sec 2 123 KBytes [ 5] 3.00-4.00 sec 11.4 MBytes 95.9 Mbits/sec 35 119 KBytes [ 5] 4.00-5.00 sec 11.5 MBytes 96.4 Mbits/sec 20 96.2 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.8 MBytes 100 Mbits/sec 145 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 1Expect this output in
DUT0:Connecting to host 192.168.100.2, port 4321 [ 5] local 192.168.100.1 port 59046 connected to 192.168.100.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.8 MBytes 124 Mbits/sec 180 107 KBytes [ 5] 1.00-2.00 sec 11.9 MBytes 100 Mbits/sec 9 99.0 KBytes [ 5] 2.00-3.00 sec 10.9 MBytes 91.7 Mbits/sec 2 136 KBytes [ 5] 3.00-4.00 sec 11.9 MBytes 100 Mbits/sec 60 123 KBytes [ 5] 4.00-5.00 sec 10.9 MBytes 91.7 Mbits/sec 11 113 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 60.6 MBytes 102 Mbits/sec 262 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: 0Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPackets."bond0" = INTEGER: 225977 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPps."bond0" = INTEGER: 8722 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBytes."bond0" = INTEGER: 137790785 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutDrops."bond0" = INTEGER: 23 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutKind."bond0" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBps."bond0" = INTEGER: 9382836 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutOverlimits."bond0" = INTEGER: 7266 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: 49787 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassPackets."bond0".2 = INTEGER: 176190 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".1 = INTEGER: 3345461 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".2 = INTEGER: 134445324 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: 3889 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPackets."bond0" = INTEGER: 854351 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPps."bond0" = INTEGER: 16627 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBytes."bond0" = INTEGER: 1275912144 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInDrops."bond0" = INTEGER: 4263 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInKind."bond0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBps."bond0" = INTEGER: 23907330 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 1Show 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.785 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.785/0.785/0.785/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 1Expect this output in
DUT1:Connecting to host 10.0.0.1, port 1234 [ 5] local 10.0.0.2 port 41624 connected to 10.0.0.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 90.9 MBytes 762 Mbits/sec 381 36.2 KBytes [ 5] 1.00-2.00 sec 206 MBytes 1.73 Gbits/sec 835 44.5 KBytes [ 5] 2.00-3.00 sec 148 MBytes 1.24 Gbits/sec 481 111 KBytes [ 5] 3.00-4.00 sec 216 MBytes 1.81 Gbits/sec 708 45.9 KBytes [ 5] 4.00-5.00 sec 295 MBytes 2.47 Gbits/sec 1192 834 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 956 MBytes 1.60 Gbits/sec 3597 sender [ 5] 0.00-5.00 sec 953 MBytes 1.60 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 1Expect this output in
DUT1:Connecting to host 10.0.0.1, port 4321 [ 5] local 10.0.0.2 port 47310 connected to 10.0.0.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 306 MBytes 2.56 Gbits/sec 967 69.5 KBytes [ 5] 1.00-2.00 sec 292 MBytes 2.45 Gbits/sec 857 47.3 KBytes [ 5] 2.00-3.01 sec 271 MBytes 2.26 Gbits/sec 1154 271 KBytes [ 5] 3.01-4.00 sec 258 MBytes 2.18 Gbits/sec 1230 398 KBytes [ 5] 4.00-5.00 sec 262 MBytes 2.20 Gbits/sec 943 82.0 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 1.36 GBytes 2.33 Gbits/sec 5151 sender [ 5] 0.00-5.00 sec 1.35 GBytes 2.33 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 1Expect this output in
DUT0:Connecting to host 10.0.0.2, port 1234 [ 5] local 10.0.0.1 port 56480 connected to 10.0.0.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.2 MBytes 119 Mbits/sec 69 98.7 KBytes [ 5] 1.00-2.00 sec 11.6 MBytes 96.9 Mbits/sec 34 96.0 KBytes [ 5] 2.00-3.00 sec 11.6 MBytes 96.9 Mbits/sec 2 135 KBytes [ 5] 3.00-4.00 sec 11.6 MBytes 96.9 Mbits/sec 22 120 KBytes [ 5] 4.00-5.00 sec 11.6 MBytes 97.4 Mbits/sec 16 84.8 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 60.4 MBytes 101 Mbits/sec 143 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 1Expect this output in
DUT0:Connecting to host 10.0.0.2, port 4321 [ 5] local 10.0.0.1 port 36732 connected to 10.0.0.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.8 MBytes 124 Mbits/sec 134 129 KBytes [ 5] 1.00-2.00 sec 11.9 MBytes 99.5 Mbits/sec 22 113 KBytes [ 5] 2.00-3.00 sec 11.1 MBytes 92.8 Mbits/sec 11 94.6 KBytes [ 5] 3.00-4.00 sec 11.9 MBytes 100 Mbits/sec 7 127 KBytes [ 5] 4.00-5.00 sec 11.1 MBytes 92.8 Mbits/sec 74 114 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 60.7 MBytes 102 Mbits/sec 248 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: 0Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutPackets."tun0" = INTEGER: 173744 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutPps."tun0" = INTEGER: 7748 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBytes."tun0" = INTEGER: 132888910 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutDrops."tun0" = INTEGER: 23 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutKind."tun0" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBps."tun0" = INTEGER: 9209717 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutOverlimits."tun0" = INTEGER: 7380 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: 40976 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassPackets."tun0".2 = INTEGER: 132768 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".1 = INTEGER: 2153386 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".2 = INTEGER: 130735524 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: 3954 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPackets."tun0" = INTEGER: 1731000 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPps."tun0" = INTEGER: 33305 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBytes."tun0" = INTEGER: 2543345307 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInDrops."tun0" = INTEGER: 961 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInKind."tun0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBps."tun0" = INTEGER: 48327918 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInOverlimits."tun0" = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInRate."tun0" = INTEGER: 0