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.430 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.430/0.430/0.430/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 37300 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 175 MBytes 1.46 Gbits/sec 619 50.9 KBytes [ 5] 1.00-2.00 sec 168 MBytes 1.41 Gbits/sec 620 42.4 KBytes [ 5] 2.00-3.00 sec 163 MBytes 1.37 Gbits/sec 593 48.1 KBytes [ 5] 3.00-4.00 sec 144 MBytes 1.21 Gbits/sec 541 36.8 KBytes [ 5] 4.00-5.00 sec 166 MBytes 1.39 Gbits/sec 607 28.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 816 MBytes 1.37 Gbits/sec 2980 sender [ 5] 0.00-5.00 sec 816 MBytes 1.37 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 51566 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 186 MBytes 1.56 Gbits/sec 668 49.5 KBytes [ 5] 1.00-2.00 sec 147 MBytes 1.23 Gbits/sec 542 21.2 KBytes [ 5] 2.00-3.00 sec 180 MBytes 1.51 Gbits/sec 639 29.7 KBytes [ 5] 3.00-4.00 sec 156 MBytes 1.31 Gbits/sec 572 35.4 KBytes [ 5] 4.00-5.00 sec 179 MBytes 1.50 Gbits/sec 622 41.0 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 847 MBytes 1.42 Gbits/sec 3043 sender [ 5] 0.00-5.00 sec 846 MBytes 1.42 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 34484 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 65 96.2 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 93.8 Mbits/sec 6 97.6 KBytes [ 5] 2.00-3.00 sec 11.7 MBytes 98.5 Mbits/sec 7 99.0 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 93.8 Mbits/sec 7 102 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 94.3 Mbits/sec 18 96.2 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.6 MBytes 100 Mbits/sec 103 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 50040 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 63 100 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 93.8 Mbits/sec 6 102 KBytes [ 5] 2.00-3.00 sec 11.2 MBytes 93.8 Mbits/sec 7 105 KBytes [ 5] 3.00-4.00 sec 11.8 MBytes 99.0 Mbits/sec 8 107 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 93.8 Mbits/sec 3 109 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.7 MBytes 100 Mbits/sec 87 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: 472821 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutPps."eth0" = INTEGER: 13059 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBytes."eth0" = INTEGER: 154193846 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: 9582437 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutOverlimits."eth0" = INTEGER: 7900 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: 187894 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassPackets."eth0".2 = INTEGER: 284927 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".1 = INTEGER: 12512478 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".2 = INTEGER: 141681368 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: 4232 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPackets."eth0" = INTEGER: 1214973 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPps."eth0" = INTEGER: 22519 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBytes."eth0" = INTEGER: 1823329001 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInDrops."eth0" = INTEGER: 6076 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInKind."eth0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBps."eth0" = INTEGER: 32968792 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.555 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.555/0.555/0.555/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 51424 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 156 MBytes 1.31 Gbits/sec 559 22.6 KBytes [ 5] 1.00-2.00 sec 157 MBytes 1.32 Gbits/sec 592 22.6 KBytes [ 5] 2.00-3.00 sec 153 MBytes 1.29 Gbits/sec 575 14.1 KBytes [ 5] 3.00-4.00 sec 143 MBytes 1.20 Gbits/sec 518 36.8 KBytes [ 5] 4.00-5.00 sec 151 MBytes 1.26 Gbits/sec 578 39.6 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 760 MBytes 1.27 Gbits/sec 2822 sender [ 5] 0.00-5.00 sec 759 MBytes 1.27 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 51048 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 175 MBytes 1.47 Gbits/sec 664 29.7 KBytes [ 5] 1.00-2.00 sec 128 MBytes 1.07 Gbits/sec 476 17.0 KBytes [ 5] 2.00-3.00 sec 122 MBytes 1.02 Gbits/sec 478 12.7 KBytes [ 5] 3.00-4.00 sec 152 MBytes 1.28 Gbits/sec 556 24.0 KBytes [ 5] 4.00-5.00 sec 150 MBytes 1.26 Gbits/sec 534 29.7 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 727 MBytes 1.22 Gbits/sec 2708 sender [ 5] 0.00-5.00 sec 726 MBytes 1.22 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 57420 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 98 107 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 93.8 Mbits/sec 26 82.0 KBytes [ 5] 2.00-3.00 sec 11.8 MBytes 99.0 Mbits/sec 13 89.1 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 93.8 Mbits/sec 17 102 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 93.8 Mbits/sec 44 106 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.5 MBytes 99.9 Mbits/sec 198 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 57106 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 83 112 KBytes [ 5] 1.00-2.00 sec 11.4 MBytes 95.9 Mbits/sec 10 119 KBytes [ 5] 2.00-3.00 sec 11.0 MBytes 92.3 Mbits/sec 9 122 KBytes [ 5] 3.00-4.00 sec 11.8 MBytes 99.0 Mbits/sec 5 120 KBytes [ 5] 4.00-5.00 sec 11.0 MBytes 92.3 Mbits/sec 6 122 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.3 MBytes 99.4 Mbits/sec 113 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: 405087 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutPps."eth0"."100" = INTEGER: 11617 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBytes."eth0"."100" = INTEGER: 149669776 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: 9539832 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutOverlimits."eth0"."100" = INTEGER: 8021 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: 172243 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassPackets."eth0"."100".2 = INTEGER: 232844 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".1 = INTEGER: 11473276 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".2 = INTEGER: 138196500 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: 4286 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPackets."eth0"."100" = INTEGER: 1084034 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPps."eth0"."100" = INTEGER: 19861 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBytes."eth0"."100" = INTEGER: 1628852252 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInDrops."eth0"."100" = INTEGER: 5571 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInKind."eth0"."100" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBps."eth0"."100" = INTEGER: 29131220 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.492 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.492/0.492/0.492/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 35944 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 163 MBytes 1.37 Gbits/sec 548 28.3 KBytes [ 5] 1.00-2.00 sec 115 MBytes 964 Mbits/sec 383 33.9 KBytes [ 5] 2.00-3.00 sec 133 MBytes 1.12 Gbits/sec 481 33.9 KBytes [ 5] 3.00-4.00 sec 157 MBytes 1.32 Gbits/sec 585 41.0 KBytes [ 5] 4.00-5.00 sec 135 MBytes 1.13 Gbits/sec 511 17.0 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 704 MBytes 1.18 Gbits/sec 2508 sender [ 5] 0.00-5.00 sec 703 MBytes 1.18 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 55320 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 132 MBytes 1.10 Gbits/sec 506 41.0 KBytes [ 5] 1.00-2.00 sec 130 MBytes 1.09 Gbits/sec 456 26.9 KBytes [ 5] 2.00-3.00 sec 157 MBytes 1.32 Gbits/sec 592 25.5 KBytes [ 5] 3.00-4.00 sec 176 MBytes 1.48 Gbits/sec 624 76.4 KBytes [ 5] 4.00-5.00 sec 168 MBytes 1.41 Gbits/sec 588 29.7 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 762 MBytes 1.28 Gbits/sec 2766 sender [ 5] 0.00-5.00 sec 761 MBytes 1.28 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 55720 connected to 192.168.100.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.4 MBytes 121 Mbits/sec 102 107 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 93.8 Mbits/sec 27 86.3 KBytes [ 5] 2.00-3.00 sec 11.2 MBytes 93.8 Mbits/sec 7 83.4 KBytes [ 5] 3.00-4.00 sec 11.7 MBytes 98.5 Mbits/sec 10 79.2 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 93.8 Mbits/sec 20 83.4 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.7 MBytes 100 Mbits/sec 166 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 57094 connected to 192.168.100.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.0 MBytes 117 Mbits/sec 29 113 KBytes [ 5] 1.00-2.00 sec 11.1 MBytes 93.3 Mbits/sec 24 82.0 KBytes [ 5] 2.00-3.00 sec 11.6 MBytes 97.0 Mbits/sec 6 86.3 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 93.8 Mbits/sec 43 83.4 KBytes [ 5] 4.00-5.00 sec 11.7 MBytes 98.5 Mbits/sec 0 97.6 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.6 MBytes 100 Mbits/sec 102 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: 419237 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutPps."br0" = INTEGER: 12280 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBytes."br0" = INTEGER: 150614817 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutDrops."br0" = INTEGER: 21 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutKind."br0" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBps."br0" = INTEGER: 9482288 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutOverlimits."br0" = INTEGER: 8592 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: 162251 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassPackets."br0".2 = INTEGER: 256986 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".1 = INTEGER: 10802843 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".2 = INTEGER: 139811974 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: 4590 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPackets."br0" = INTEGER: 1067492 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPps."br0" = INTEGER: 20394 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBytes."br0" = INTEGER: 1605735779 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInDrops."br0" = INTEGER: 5312 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInKind."br0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBps."br0" = INTEGER: 30135315 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.362 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.362/0.362/0.362/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 58618 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 192 MBytes 1.61 Gbits/sec 696 31.1 KBytes [ 5] 1.00-2.00 sec 192 MBytes 1.61 Gbits/sec 673 18.4 KBytes [ 5] 2.00-3.00 sec 201 MBytes 1.69 Gbits/sec 725 48.1 KBytes [ 5] 3.00-4.00 sec 178 MBytes 1.50 Gbits/sec 656 39.6 KBytes [ 5] 4.00-5.00 sec 180 MBytes 1.51 Gbits/sec 673 18.4 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 943 MBytes 1.58 Gbits/sec 3423 sender [ 5] 0.00-5.00 sec 943 MBytes 1.58 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 45680 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 172 MBytes 1.44 Gbits/sec 614 36.8 KBytes [ 5] 1.00-2.00 sec 158 MBytes 1.33 Gbits/sec 553 25.5 KBytes [ 5] 2.00-3.00 sec 156 MBytes 1.31 Gbits/sec 529 41.0 KBytes [ 5] 3.00-4.00 sec 150 MBytes 1.26 Gbits/sec 555 28.3 KBytes [ 5] 4.00-5.00 sec 176 MBytes 1.48 Gbits/sec 656 35.4 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 812 MBytes 1.36 Gbits/sec 2907 sender [ 5] 0.00-5.00 sec 811 MBytes 1.36 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 36064 connected to 192.168.100.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.5 MBytes 122 Mbits/sec 120 86.3 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 93.8 Mbits/sec 5 117 KBytes [ 5] 2.00-3.00 sec 11.9 MBytes 100 Mbits/sec 7 119 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 94.4 Mbits/sec 8 122 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 93.8 Mbits/sec 5 122 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 60.0 MBytes 101 Mbits/sec 145 sender [ 5] 0.00-5.01 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 43894 connected to 192.168.100.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 13.8 MBytes 116 Mbits/sec 102 123 KBytes [ 5] 1.00-2.00 sec 11.4 MBytes 95.9 Mbits/sec 63 84.8 KBytes [ 5] 2.00-3.00 sec 11.5 MBytes 96.4 Mbits/sec 7 86.3 KBytes [ 5] 3.00-4.00 sec 11.5 MBytes 96.4 Mbits/sec 9 115 KBytes [ 5] 4.00-5.00 sec 11.6 MBytes 97.0 Mbits/sec 13 106 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.8 MBytes 100 Mbits/sec 194 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: 489163 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutPps."br0"."100" = INTEGER: 13098 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBytes."br0"."100" = INTEGER: 155239491 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: 9660414 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutOverlimits."br0"."100" = INTEGER: 7660 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: 221983 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassPackets."br0"."100".2 = INTEGER: 267180 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".1 = INTEGER: 14772394 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".2 = INTEGER: 140467097 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: 4112 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPackets."br0"."100" = INTEGER: 1280539 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPps."br0"."100" = INTEGER: 22956 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBytes."br0"."100" = INTEGER: 1923969359 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInDrops."br0"."100" = INTEGER: 6373 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInKind."br0"."100" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBps."br0"."100" = INTEGER: 33735699 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.506 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.506/0.506/0.506/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 52132 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 222 MBytes 1.87 Gbits/sec 833 45.2 KBytes [ 5] 1.00-2.00 sec 200 MBytes 1.68 Gbits/sec 708 26.9 KBytes [ 5] 2.00-3.00 sec 192 MBytes 1.61 Gbits/sec 730 32.5 KBytes [ 5] 3.00-4.00 sec 194 MBytes 1.63 Gbits/sec 800 38.2 KBytes [ 5] 4.00-5.00 sec 186 MBytes 1.56 Gbits/sec 640 28.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 995 MBytes 1.67 Gbits/sec 3711 sender [ 5] 0.00-5.00 sec 994 MBytes 1.67 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 43610 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 80.9 MBytes 679 Mbits/sec 294 24.0 KBytes [ 5] 1.00-2.00 sec 119 MBytes 1.00 Gbits/sec 432 26.9 KBytes [ 5] 2.00-3.00 sec 155 MBytes 1.30 Gbits/sec 594 17.0 KBytes [ 5] 3.00-4.00 sec 62.4 MBytes 523 Mbits/sec 215 22.6 KBytes [ 5] 4.00-5.00 sec 119 MBytes 1.00 Gbits/sec 424 25.5 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 537 MBytes 902 Mbits/sec 1959 sender [ 5] 0.00-5.00 sec 537 MBytes 901 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 48206 connected to 192.168.100.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 12.5 MBytes 105 Mbits/sec 176 129 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 93.8 Mbits/sec 80 117 KBytes [ 5] 2.00-3.00 sec 12.1 MBytes 102 Mbits/sec 12 109 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 93.8 Mbits/sec 15 100 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 94.3 Mbits/sec 3 137 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 58.2 MBytes 97.7 Mbits/sec 286 sender [ 5] 0.00-5.00 sec 56.1 MBytes 94.1 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 34548 connected to 192.168.100.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.2 MBytes 119 Mbits/sec 96 103 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 93.8 Mbits/sec 6 103 KBytes [ 5] 2.00-3.00 sec 11.8 MBytes 99.0 Mbits/sec 9 97.6 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 93.8 Mbits/sec 4 96.2 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 94.4 Mbits/sec 6 99.0 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.7 MBytes 100 Mbits/sec 121 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: 0Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPackets."bond0" = INTEGER: 325912 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPps."bond0" = INTEGER: 10183 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBytes."bond0" = INTEGER: 142045810 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: 9347367 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutOverlimits."bond0" = INTEGER: 7427 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: 132252 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassPackets."bond0".2 = INTEGER: 193660 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".1 = INTEGER: 8864603 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".2 = INTEGER: 133181207 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: 3966 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPackets."bond0" = INTEGER: 1118467 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPps."bond0" = INTEGER: 18460 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBytes."bond0" = INTEGER: 1679249874 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInDrops."bond0" = INTEGER: 5716 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInKind."bond0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBps."bond0" = INTEGER: 26939780 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.441 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.441/0.441/0.441/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 41430 connected to 10.0.0.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 361 MBytes 3.03 Gbits/sec 1514 129 KBytes [ 5] 1.00-2.00 sec 316 MBytes 2.65 Gbits/sec 1062 45.9 KBytes [ 5] 2.00-3.00 sec 301 MBytes 2.53 Gbits/sec 1145 186 KBytes [ 5] 3.00-4.00 sec 330 MBytes 2.77 Gbits/sec 1321 207 KBytes [ 5] 4.00-5.00 sec 246 MBytes 2.07 Gbits/sec 934 55.6 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 1.52 GBytes 2.61 Gbits/sec 5976 sender [ 5] 0.00-5.00 sec 1.52 GBytes 2.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 37150 connected to 10.0.0.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 296 MBytes 2.48 Gbits/sec 945 154 KBytes [ 5] 1.00-2.00 sec 212 MBytes 1.77 Gbits/sec 779 34.8 KBytes [ 5] 2.00-3.00 sec 238 MBytes 2.00 Gbits/sec 1007 90.4 KBytes [ 5] 3.00-4.00 sec 312 MBytes 2.62 Gbits/sec 862 80.7 KBytes [ 5] 4.00-5.00 sec 270 MBytes 2.26 Gbits/sec 1071 44.5 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 1.30 GBytes 2.23 Gbits/sec 4664 sender [ 5] 0.00-5.00 sec 1.29 GBytes 2.22 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 58652 connected to 10.0.0.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 15.6 MBytes 131 Mbits/sec 252 82.0 KBytes [ 5] 1.00-2.00 sec 12.5 MBytes 105 Mbits/sec 8 90.4 KBytes [ 5] 2.00-3.00 sec 11.2 MBytes 94.4 Mbits/sec 8 97.3 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 94.4 Mbits/sec 9 82.0 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 94.4 Mbits/sec 8 104 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 61.9 MBytes 104 Mbits/sec 285 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 49776 connected to 10.0.0.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 16.6 MBytes 139 Mbits/sec 211 107 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 94.4 Mbits/sec 78 80.7 KBytes [ 5] 2.00-3.00 sec 11.2 MBytes 94.4 Mbits/sec 36 94.6 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 94.4 Mbits/sec 10 103 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 94.4 Mbits/sec 7 118 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 61.6 MBytes 103 Mbits/sec 342 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: 185900 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutPps."tun0" = INTEGER: 7755 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBytes."tun0" = INTEGER: 133556405 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutDrops."tun0" = INTEGER: 25 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutKind."tun0" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBps."tun0" = INTEGER: 9155956 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutOverlimits."tun0" = INTEGER: 8346 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: 54019 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassPackets."tun0".2 = INTEGER: 131881 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".1 = INTEGER: 2835511 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".2 = INTEGER: 130720894 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: 4456 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPackets."tun0" = INTEGER: 2123429 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPps."tun0" = INTEGER: 35831 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBytes."tun0" = INTEGER: 3126325422 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInDrops."tun0" = INTEGER: 1020 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInKind."tun0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBps."tun0" = INTEGER: 52331657 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInOverlimits."tun0" = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInRate."tun0" = INTEGER: 0