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 the 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.526 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.526/0.526/0.526/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 the following output on
DUT1:Connecting to host 192.168.100.1, port 1234 [ 5] local 192.168.100.2 port 57188 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 102 MBytes 859 Mbits/sec 326 59.4 KBytes [ 5] 1.00-2.00 sec 92.5 MBytes 776 Mbits/sec 322 31.1 KBytes [ 5] 2.00-3.00 sec 82.8 MBytes 694 Mbits/sec 299 22.6 KBytes [ 5] 3.00-4.00 sec 88.4 MBytes 742 Mbits/sec 329 11.3 KBytes [ 5] 4.00-5.00 sec 87.2 MBytes 732 Mbits/sec 311 28.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 453 MBytes 760 Mbits/sec 1587 sender [ 5] 0.00-5.00 sec 453 MBytes 759 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 the following output on
DUT1:Connecting to host 192.168.100.1, port 4321 [ 5] local 192.168.100.2 port 53650 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 129 MBytes 1.08 Gbits/sec 466 21.2 KBytes [ 5] 1.00-2.00 sec 140 MBytes 1.17 Gbits/sec 521 35.4 KBytes [ 5] 2.00-3.00 sec 130 MBytes 1.09 Gbits/sec 471 59.4 KBytes [ 5] 3.00-4.00 sec 99.2 MBytes 832 Mbits/sec 352 38.2 KBytes [ 5] 4.00-5.00 sec 153 MBytes 1.28 Gbits/sec 547 36.8 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 652 MBytes 1.09 Gbits/sec 2357 sender [ 5] 0.00-5.00 sec 651 MBytes 1.09 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 the following output on
DUT0:Connecting to host 192.168.100.2, port 1234 [ 5] local 192.168.100.1 port 57470 connected to 192.168.100.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 13.7 MBytes 115 Mbits/sec 146 87.7 KBytes [ 5] 1.00-2.00 sec 11.5 MBytes 96.4 Mbits/sec 62 91.9 KBytes [ 5] 2.00-3.00 sec 11.4 MBytes 95.9 Mbits/sec 68 94.7 KBytes [ 5] 3.00-4.00 sec 11.6 MBytes 97.0 Mbits/sec 64 97.6 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 93.8 Mbits/sec 93 66.5 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.4 MBytes 99.6 Mbits/sec 433 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 the following output on
DUT0:Connecting to host 192.168.100.2, port 4321 [ 5] local 192.168.100.1 port 51780 connected to 192.168.100.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 13.9 MBytes 116 Mbits/sec 184 77.8 KBytes [ 5] 1.00-2.00 sec 11.6 MBytes 97.0 Mbits/sec 48 89.1 KBytes [ 5] 2.00-3.00 sec 11.6 MBytes 97.0 Mbits/sec 65 82.0 KBytes [ 5] 3.00-4.00 sec 11.1 MBytes 93.3 Mbits/sec 81 84.8 KBytes [ 5] 4.00-5.00 sec 11.4 MBytes 95.9 Mbits/sec 70 86.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.5 MBytes 99.9 Mbits/sec 448 sender [ 5] 0.00-5.00 sec 58.5 MBytes 98.0 Mbits/sec receiver iperf Done.
Step 8: Run the command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl on DUT0 and check whether the 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: 204304 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutPps."eth0" = INTEGER: 8356 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBytes."eth0" = INTEGER: 136364820 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutDrops."eth0" = INTEGER: 34 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutKind."eth0" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBps."eth0" = INTEGER: 9066428 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutOverlimits."eth0" = INTEGER: 7522 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: 44775 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassPackets."eth0".2 = INTEGER: 159529 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".1 = INTEGER: 3020972 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".2 = INTEGER: 133343848 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: 3955 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPackets."eth0" = INTEGER: 807725 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPps."eth0" = INTEGER: 16795 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBytes."eth0" = INTEGER: 1210517848 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInDrops."eth0" = INTEGER: 3992 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInKind."eth0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBps."eth0" = INTEGER: 24622448 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 the 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.835 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.835/0.835/0.835/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 the following output on
DUT1:Connecting to host 192.168.100.1, port 1234 [ 5] local 192.168.100.2 port 50770 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 154 MBytes 1.29 Gbits/sec 541 48.1 KBytes [ 5] 1.00-2.00 sec 168 MBytes 1.41 Gbits/sec 628 25.5 KBytes [ 5] 2.00-3.00 sec 145 MBytes 1.21 Gbits/sec 491 36.8 KBytes [ 5] 3.00-4.00 sec 194 MBytes 1.62 Gbits/sec 747 41.0 KBytes [ 5] 4.00-5.00 sec 208 MBytes 1.74 Gbits/sec 799 33.9 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 868 MBytes 1.46 Gbits/sec 3206 sender [ 5] 0.00-5.00 sec 868 MBytes 1.46 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 the following output on
DUT1:Connecting to host 192.168.100.1, port 4321 [ 5] local 192.168.100.2 port 36836 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 154 MBytes 1.29 Gbits/sec 528 48.1 KBytes [ 5] 1.00-2.00 sec 142 MBytes 1.19 Gbits/sec 548 25.5 KBytes [ 5] 2.00-3.00 sec 86.2 MBytes 723 Mbits/sec 274 17.0 KBytes [ 5] 3.00-4.00 sec 122 MBytes 1.03 Gbits/sec 451 31.1 KBytes [ 5] 4.00-5.00 sec 118 MBytes 987 Mbits/sec 398 24.0 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 622 MBytes 1.04 Gbits/sec 2199 sender [ 5] 0.00-5.00 sec 621 MBytes 1.04 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 the following output on
DUT0:Connecting to host 192.168.100.2, port 1234 [ 5] local 192.168.100.1 port 49736 connected to 192.168.100.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 13.9 MBytes 116 Mbits/sec 139 94.7 KBytes [ 5] 1.00-2.00 sec 11.5 MBytes 96.4 Mbits/sec 91 69.3 KBytes [ 5] 2.00-3.00 sec 11.4 MBytes 95.9 Mbits/sec 73 77.8 KBytes [ 5] 3.00-4.00 sec 11.1 MBytes 93.3 Mbits/sec 74 80.6 KBytes [ 5] 4.00-5.00 sec 11.4 MBytes 95.9 Mbits/sec 66 86.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.4 MBytes 99.6 Mbits/sec 443 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 the following output on
DUT0:Connecting to host 192.168.100.2, port 4321 [ 5] local 192.168.100.1 port 47738 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 153 82.0 KBytes [ 5] 1.00-2.00 sec 11.4 MBytes 95.4 Mbits/sec 67 82.0 KBytes [ 5] 2.00-3.00 sec 11.4 MBytes 95.9 Mbits/sec 67 84.8 KBytes [ 5] 3.00-4.00 sec 11.4 MBytes 95.9 Mbits/sec 33 109 KBytes [ 5] 4.00-5.00 sec 11.4 MBytes 95.9 Mbits/sec 74 91.9 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.4 MBytes 99.7 Mbits/sec 394 sender [ 5] 0.00-5.00 sec 58.4 MBytes 98.0 Mbits/sec receiver iperf Done.
Step 8: Run the command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl on DUT0 and check whether the 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: 245839 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutPps."eth0"."100" = INTEGER: 8691 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBytes."eth0"."100" = INTEGER: 139183243 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutDrops."eth0"."100" = INTEGER: 33 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutKind."eth0"."100" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBps."eth0"."100" = INTEGER: 9193369 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutOverlimits."eth0"."100" = INTEGER: 7451 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: 98650 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassPackets."eth0"."100".2 = INTEGER: 147189 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".1 = INTEGER: 6631194 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".2 = INTEGER: 132552049 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: 3917 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPackets."eth0"."100" = INTEGER: 1086382 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPps."eth0"."100" = INTEGER: 19424 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBytes."eth0"."100" = INTEGER: 1632731234 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInDrops."eth0"."100" = INTEGER: 5445 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInKind."eth0"."100" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBps."eth0"."100" = INTEGER: 28605636 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 the 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.392 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.392/0.392/0.392/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 the following output on
DUT1:Connecting to host 192.168.100.1, port 1234 [ 5] local 192.168.100.2 port 34092 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 161 MBytes 1.35 Gbits/sec 553 15.6 KBytes [ 5] 1.00-2.00 sec 187 MBytes 1.56 Gbits/sec 682 36.8 KBytes [ 5] 2.00-3.00 sec 133 MBytes 1.12 Gbits/sec 477 28.3 KBytes [ 5] 3.00-4.00 sec 141 MBytes 1.18 Gbits/sec 533 28.3 KBytes [ 5] 4.00-5.00 sec 130 MBytes 1.09 Gbits/sec 516 38.2 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 752 MBytes 1.26 Gbits/sec 2761 sender [ 5] 0.00-5.00 sec 751 MBytes 1.26 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 the following output on
DUT1:Connecting to host 192.168.100.1, port 4321 [ 5] local 192.168.100.2 port 53310 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 116 MBytes 975 Mbits/sec 391 39.6 KBytes [ 5] 1.00-2.00 sec 86.7 MBytes 728 Mbits/sec 322 24.0 KBytes [ 5] 2.00-3.00 sec 115 MBytes 961 Mbits/sec 395 24.0 KBytes [ 5] 3.00-4.00 sec 162 MBytes 1.36 Gbits/sec 592 31.1 KBytes [ 5] 4.00-5.00 sec 115 MBytes 968 Mbits/sec 424 26.9 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 595 MBytes 998 Mbits/sec 2124 sender [ 5] 0.00-5.00 sec 594 MBytes 997 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 the following output on
DUT0:Connecting to host 192.168.100.2, port 1234 [ 5] local 192.168.100.1 port 35544 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 157 87.7 KBytes [ 5] 1.00-2.00 sec 11.4 MBytes 95.9 Mbits/sec 62 93.3 KBytes [ 5] 2.00-3.00 sec 11.4 MBytes 95.9 Mbits/sec 95 66.5 KBytes [ 5] 3.00-4.00 sec 11.0 MBytes 92.3 Mbits/sec 65 76.4 KBytes [ 5] 4.00-5.00 sec 11.6 MBytes 97.0 Mbits/sec 63 100 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.6 MBytes 100 Mbits/sec 442 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 the following output on
DUT0:Connecting to host 192.168.100.2, port 4321 [ 5] local 192.168.100.1 port 57126 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 153 70.7 KBytes [ 5] 1.00-2.00 sec 11.3 MBytes 94.9 Mbits/sec 74 86.3 KBytes [ 5] 2.00-3.00 sec 11.4 MBytes 95.9 Mbits/sec 71 94.7 KBytes [ 5] 3.00-4.00 sec 11.4 MBytes 95.4 Mbits/sec 94 70.7 KBytes [ 5] 4.00-5.00 sec 11.3 MBytes 94.9 Mbits/sec 70 73.5 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.4 MBytes 99.7 Mbits/sec 462 sender [ 5] 0.00-5.00 sec 58.4 MBytes 98.0 Mbits/sec receiver iperf Done.
Step 8: Run the command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl on DUT0 and check whether the 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: 241077 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutPps."br0" = INTEGER: 8705 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBytes."br0" = INTEGER: 138831989 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutDrops."br0" = INTEGER: 35 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutKind."br0" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBps."br0" = INTEGER: 9139605 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutOverlimits."br0" = INTEGER: 7960 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: 89040 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassPackets."br0".2 = INTEGER: 152037 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".1 = INTEGER: 5980426 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".2 = INTEGER: 132851563 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: 4194 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPackets."br0" = INTEGER: 983750 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPps."br0" = INTEGER: 18232 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBytes."br0" = INTEGER: 1475824089 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInDrops."br0" = INTEGER: 4935 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInKind."br0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBps."br0" = INTEGER: 26674421 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 the 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.834 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.834/0.834/0.834/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 the following output on
DUT1:Connecting to host 192.168.100.1, port 1234 [ 5] local 192.168.100.2 port 49050 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 488 39.6 KBytes [ 5] 1.00-2.00 sec 164 MBytes 1.38 Gbits/sec 602 33.9 KBytes [ 5] 2.00-3.00 sec 136 MBytes 1.14 Gbits/sec 487 22.6 KBytes [ 5] 3.00-4.00 sec 185 MBytes 1.55 Gbits/sec 685 42.4 KBytes [ 5] 4.00-5.00 sec 155 MBytes 1.30 Gbits/sec 575 18.4 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 777 MBytes 1.30 Gbits/sec 2837 sender [ 5] 0.00-5.00 sec 776 MBytes 1.30 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 the following output on
DUT1:Connecting to host 192.168.100.1, port 4321 [ 5] local 192.168.100.2 port 54436 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 139 MBytes 1.16 Gbits/sec 529 24.0 KBytes [ 5] 1.00-2.00 sec 127 MBytes 1.06 Gbits/sec 452 19.8 KBytes [ 5] 2.00-3.00 sec 128 MBytes 1.07 Gbits/sec 489 41.0 KBytes [ 5] 3.00-4.00 sec 176 MBytes 1.48 Gbits/sec 673 43.8 KBytes [ 5] 4.00-5.00 sec 163 MBytes 1.37 Gbits/sec 592 58.0 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 733 MBytes 1.23 Gbits/sec 2735 sender [ 5] 0.00-5.00 sec 733 MBytes 1.23 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 the following output on
DUT0:Connecting to host 192.168.100.2, port 1234 [ 5] local 192.168.100.1 port 35448 connected to 192.168.100.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 13.8 MBytes 116 Mbits/sec 169 83.4 KBytes [ 5] 1.00-2.00 sec 11.4 MBytes 95.9 Mbits/sec 78 77.8 KBytes [ 5] 2.00-3.00 sec 11.6 MBytes 97.5 Mbits/sec 89 66.5 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 93.8 Mbits/sec 25 113 KBytes [ 5] 4.00-5.00 sec 11.7 MBytes 98.5 Mbits/sec 68 93.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.8 MBytes 100 Mbits/sec 429 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 the following output on
DUT0:Connecting to host 192.168.100.2, port 4321 [ 5] local 192.168.100.1 port 43018 connected to 192.168.100.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.1 MBytes 118 Mbits/sec 183 76.4 KBytes [ 5] 1.00-2.00 sec 11.3 MBytes 94.9 Mbits/sec 61 103 KBytes [ 5] 2.00-3.00 sec 11.7 MBytes 98.5 Mbits/sec 71 82.0 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 94.3 Mbits/sec 61 109 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 93.8 Mbits/sec 75 94.7 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.6 MBytes 100 Mbits/sec 451 sender [ 5] 0.00-5.00 sec 58.5 MBytes 98.0 Mbits/sec receiver iperf Done.
Step 8: Run the command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl on DUT0 and check whether the 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: 255193 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutPps."br0"."100" = INTEGER: 9155 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBytes."br0"."100" = INTEGER: 139824612 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutDrops."br0"."100" = INTEGER: 30 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutKind."br0"."100" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBps."br0"."100" = INTEGER: 9111760 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutOverlimits."br0"."100" = INTEGER: 6981 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: 88119 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassPackets."br0"."100".2 = INTEGER: 167074 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".1 = INTEGER: 5921443 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".2 = INTEGER: 133903169 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: 3669 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPackets."br0"."100" = INTEGER: 1100215 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPps."br0"."100" = INTEGER: 21518 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBytes."br0"."100" = INTEGER: 1655003492 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInDrops."br0"."100" = INTEGER: 5617 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInKind."br0"."100" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBps."br0"."100" = INTEGER: 31851128 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 the 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.821 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.821/0.821/0.821/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 the following output on
DUT1:Connecting to host 192.168.100.1, port 1234 [ 5] local 192.168.100.2 port 39396 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 168 MBytes 1.41 Gbits/sec 594 33.9 KBytes [ 5] 1.00-2.00 sec 136 MBytes 1.14 Gbits/sec 487 41.0 KBytes [ 5] 2.00-3.00 sec 190 MBytes 1.60 Gbits/sec 693 33.9 KBytes [ 5] 3.00-4.00 sec 161 MBytes 1.35 Gbits/sec 545 32.5 KBytes [ 5] 4.00-5.00 sec 140 MBytes 1.18 Gbits/sec 500 41.0 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 796 MBytes 1.34 Gbits/sec 2819 sender [ 5] 0.00-5.00 sec 795 MBytes 1.33 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 the following output on
DUT1:Connecting to host 192.168.100.1, port 4321 [ 5] local 192.168.100.2 port 42006 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 79.3 MBytes 665 Mbits/sec 254 22.6 KBytes [ 5] 1.00-2.00 sec 81.0 MBytes 680 Mbits/sec 313 35.4 KBytes [ 5] 2.00-3.00 sec 77.6 MBytes 651 Mbits/sec 297 29.7 KBytes [ 5] 3.00-4.00 sec 111 MBytes 928 Mbits/sec 413 39.6 KBytes [ 5] 4.00-5.00 sec 164 MBytes 1.37 Gbits/sec 583 15.6 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 512 MBytes 859 Mbits/sec 1860 sender [ 5] 0.00-5.00 sec 511 MBytes 856 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 the following output on
DUT0:Connecting to host 192.168.100.2, port 1234 [ 5] local 192.168.100.1 port 34020 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 158 53.7 KBytes [ 5] 1.00-2.00 sec 11.7 MBytes 98.5 Mbits/sec 70 70.7 KBytes [ 5] 2.00-3.00 sec 11.1 MBytes 92.8 Mbits/sec 70 73.5 KBytes [ 5] 3.00-4.00 sec 11.7 MBytes 98.0 Mbits/sec 69 79.2 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 94.3 Mbits/sec 64 86.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.6 MBytes 100 Mbits/sec 431 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 the following output on
DUT0:Connecting to host 192.168.100.2, port 4321 [ 5] local 192.168.100.1 port 39410 connected to 192.168.100.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.1 MBytes 118 Mbits/sec 151 77.8 KBytes [ 5] 1.00-2.00 sec 11.3 MBytes 94.9 Mbits/sec 72 73.5 KBytes [ 5] 2.00-3.00 sec 11.2 MBytes 93.8 Mbits/sec 70 79.2 KBytes [ 5] 3.00-4.00 sec 11.3 MBytes 94.9 Mbits/sec 73 70.7 KBytes [ 5] 4.00-5.00 sec 11.5 MBytes 96.4 Mbits/sec 69 80.6 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.4 MBytes 99.6 Mbits/sec 435 sender [ 5] 0.00-5.00 sec 58.4 MBytes 98.0 Mbits/sec receiver iperf Done.
Step 8: Run the command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl on DUT0 and check whether the 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: 238838 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPps."bond0" = INTEGER: 8706 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBytes."bond0" = INTEGER: 138690911 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutDrops."bond0" = INTEGER: 35 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutKind."bond0" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBps."bond0" = INTEGER: 9107978 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutOverlimits."bond0" = INTEGER: 7841 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: 97411 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassPackets."bond0".2 = INTEGER: 141427 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".1 = INTEGER: 6536280 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".2 = INTEGER: 132154631 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: 4125 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPackets."bond0" = INTEGER: 955160 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPps."bond0" = INTEGER: 18115 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBytes."bond0" = INTEGER: 1432530438 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInDrops."bond0" = INTEGER: 4726 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInKind."bond0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBps."bond0" = INTEGER: 26501336 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 the 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.764 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.764/0.764/0.764/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 the following output on
DUT1:Connecting to host 10.0.0.1, port 1234 [ 5] local 10.0.0.2 port 42472 connected to 10.0.0.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 243 MBytes 2.04 Gbits/sec 922 184 KBytes [ 5] 1.00-2.00 sec 268 MBytes 2.24 Gbits/sec 1073 36.2 KBytes [ 5] 2.00-3.00 sec 261 MBytes 2.19 Gbits/sec 948 620 KBytes [ 5] 3.00-4.00 sec 268 MBytes 2.24 Gbits/sec 965 149 KBytes [ 5] 4.00-5.00 sec 205 MBytes 1.72 Gbits/sec 718 145 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 1.22 GBytes 2.09 Gbits/sec 4626 sender [ 5] 0.00-5.00 sec 1.21 GBytes 2.08 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 the following output on
DUT1:Connecting to host 10.0.0.1, port 4321 [ 5] local 10.0.0.2 port 50752 connected to 10.0.0.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 245 MBytes 2.05 Gbits/sec 910 343 KBytes [ 5] 1.00-2.00 sec 226 MBytes 1.90 Gbits/sec 816 77.9 KBytes [ 5] 2.00-3.00 sec 236 MBytes 1.98 Gbits/sec 836 57.0 KBytes [ 5] 3.00-4.00 sec 280 MBytes 2.35 Gbits/sec 991 40.3 KBytes [ 5] 4.00-5.00 sec 252 MBytes 2.12 Gbits/sec 724 40.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 1.21 GBytes 2.08 Gbits/sec 4277 sender [ 5] 0.00-5.00 sec 1.21 GBytes 2.07 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 the following output on
DUT0:Connecting to host 10.0.0.2, port 1234 [ 5] local 10.0.0.1 port 41252 connected to 10.0.0.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.5 MBytes 122 Mbits/sec 171 91.8 KBytes [ 5] 1.00-2.00 sec 11.1 MBytes 93.3 Mbits/sec 96 66.8 KBytes [ 5] 2.00-3.00 sec 11.6 MBytes 97.4 Mbits/sec 51 77.9 KBytes [ 5] 3.00-4.00 sec 11.6 MBytes 96.9 Mbits/sec 83 86.2 KBytes [ 5] 4.00-5.00 sec 11.6 MBytes 97.4 Mbits/sec 76 73.7 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 60.4 MBytes 101 Mbits/sec 477 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 the following output on
DUT0:Connecting to host 10.0.0.2, port 4321 [ 5] local 10.0.0.1 port 40750 connected to 10.0.0.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.4 MBytes 121 Mbits/sec 173 82.0 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 94.3 Mbits/sec 66 68.1 KBytes [ 5] 2.00-3.00 sec 11.7 MBytes 98.4 Mbits/sec 50 76.5 KBytes [ 5] 3.00-4.00 sec 11.4 MBytes 95.4 Mbits/sec 65 79.3 KBytes [ 5] 4.00-5.00 sec 11.7 MBytes 97.9 Mbits/sec 70 73.7 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 60.4 MBytes 101 Mbits/sec 424 sender [ 5] 0.00-5.00 sec 59.0 MBytes 98.9 Mbits/sec receiver iperf Done.
Step 8: Run the command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl on DUT0 and check whether the 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: 145262 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutPps."tun0" = INTEGER: 7145 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBytes."tun0" = INTEGER: 131388403 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutDrops."tun0" = INTEGER: 33 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutKind."tun0" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBps."tun0" = INTEGER: 8951472 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutOverlimits."tun0" = INTEGER: 7368 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: 28851 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassPackets."tun0".2 = INTEGER: 116411 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".1 = INTEGER: 1516479 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".2 = INTEGER: 129871924 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: 3877 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPackets."tun0" = INTEGER: 1829367 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPps."tun0" = INTEGER: 31035 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBytes."tun0" = INTEGER: 2693659990 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInDrops."tun0" = INTEGER: 708 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInKind."tun0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBps."tun0" = INTEGER: 45359536 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInOverlimits."tun0" = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInRate."tun0" = INTEGER: 0