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=1.22 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.220/1.220/1.220/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 36942 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 129 MBytes 1.08 Gbits/sec 451 35.4 KBytes [ 5] 1.00-2.00 sec 169 MBytes 1.42 Gbits/sec 610 43.8 KBytes [ 5] 2.00-3.00 sec 176 MBytes 1.48 Gbits/sec 645 43.8 KBytes [ 5] 3.00-4.00 sec 148 MBytes 1.24 Gbits/sec 546 43.8 KBytes [ 5] 4.00-5.00 sec 158 MBytes 1.32 Gbits/sec 554 25.5 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 780 MBytes 1.31 Gbits/sec 2806 sender [ 5] 0.00-5.00 sec 780 MBytes 1.31 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 43334 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 137 MBytes 1.15 Gbits/sec 513 33.9 KBytes [ 5] 1.00-2.00 sec 156 MBytes 1.31 Gbits/sec 576 33.9 KBytes [ 5] 2.00-3.00 sec 129 MBytes 1.08 Gbits/sec 454 31.1 KBytes [ 5] 3.00-4.00 sec 139 MBytes 1.16 Gbits/sec 495 48.1 KBytes [ 5] 4.00-5.00 sec 185 MBytes 1.55 Gbits/sec 678 35.4 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 746 MBytes 1.25 Gbits/sec 2716 sender [ 5] 0.00-5.00 sec 745 MBytes 1.25 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 45814 connected to 192.168.100.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.3 MBytes 120 Mbits/sec 179 96.2 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 93.8 Mbits/sec 82 99.0 KBytes [ 5] 2.00-3.00 sec 11.2 MBytes 94.4 Mbits/sec 73 100 KBytes [ 5] 3.00-4.00 sec 11.7 MBytes 98.5 Mbits/sec 93 70.7 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 93.8 Mbits/sec 85 69.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.6 MBytes 100 Mbits/sec 512 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 51264 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 177 87.7 KBytes [ 5] 1.00-2.00 sec 11.4 MBytes 95.9 Mbits/sec 72 70.7 KBytes [ 5] 2.00-3.00 sec 11.5 MBytes 96.4 Mbits/sec 72 69.3 KBytes [ 5] 3.00-4.00 sec 11.1 MBytes 92.8 Mbits/sec 74 77.8 KBytes [ 5] 4.00-5.00 sec 11.5 MBytes 96.4 Mbits/sec 66 83.4 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.6 MBytes 99.9 Mbits/sec 461 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::telOSDxMonDBInterfacesEthernetTrafficControlOutPackets."eth0" = INTEGER: 269781 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutPps."eth0" = INTEGER: 9453 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBytes."eth0" = INTEGER: 140710496 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutDrops."eth0" = INTEGER: 35 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutKind."eth0" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBps."eth0" = INTEGER: 9201565 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutOverlimits."eth0" = INTEGER: 7781 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: 96107 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassPackets."eth0".2 = INTEGER: 173674 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".1 = INTEGER: 6448298 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".2 = INTEGER: 134262198 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: 4098 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPackets."eth0" = INTEGER: 1113410 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPps."eth0" = INTEGER: 21768 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBytes."eth0" = INTEGER: 1672731398 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInDrops."eth0" = INTEGER: 5576 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInKind."eth0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBps."eth0" = INTEGER: 32111279 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.688 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.688/0.688/0.688/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 57888 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 177 MBytes 1.48 Gbits/sec 644 29.7 KBytes [ 5] 1.00-2.00 sec 138 MBytes 1.16 Gbits/sec 552 28.3 KBytes [ 5] 2.00-3.00 sec 185 MBytes 1.55 Gbits/sec 692 38.2 KBytes [ 5] 3.00-4.00 sec 157 MBytes 1.31 Gbits/sec 552 60.8 KBytes [ 5] 4.00-5.00 sec 173 MBytes 1.45 Gbits/sec 705 28.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 829 MBytes 1.39 Gbits/sec 3145 sender [ 5] 0.00-5.00 sec 828 MBytes 1.39 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 35252 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 127 MBytes 1.06 Gbits/sec 475 15.6 KBytes [ 5] 1.00-2.00 sec 110 MBytes 921 Mbits/sec 398 24.0 KBytes [ 5] 2.00-3.00 sec 137 MBytes 1.15 Gbits/sec 537 86.3 KBytes [ 5] 3.00-4.00 sec 138 MBytes 1.16 Gbits/sec 515 35.4 KBytes [ 5] 4.00-5.01 sec 113 MBytes 941 Mbits/sec 455 41.0 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.01 sec 625 MBytes 1.05 Gbits/sec 2380 sender [ 5] 0.00-5.01 sec 624 MBytes 1.05 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 35256 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 130 102 KBytes [ 5] 1.00-2.00 sec 11.4 MBytes 95.4 Mbits/sec 91 70.7 KBytes [ 5] 2.00-3.00 sec 11.3 MBytes 94.9 Mbits/sec 57 72.1 KBytes [ 5] 3.00-4.00 sec 11.6 MBytes 97.0 Mbits/sec 88 84.8 KBytes [ 5] 4.00-5.00 sec 11.4 MBytes 95.9 Mbits/sec 51 87.7 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.6 MBytes 99.9 Mbits/sec 417 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 38352 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 160 87.7 KBytes [ 5] 1.00-2.00 sec 11.7 MBytes 98.5 Mbits/sec 72 91.9 KBytes [ 5] 2.00-3.00 sec 11.2 MBytes 94.4 Mbits/sec 68 100 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 93.8 Mbits/sec 98 65.0 KBytes [ 5] 4.00-5.00 sec 11.8 MBytes 99.0 Mbits/sec 70 76.4 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.8 MBytes 100 Mbits/sec 468 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::telOSDxMonDBInterfacesEthernetVifTrafficControlOutPackets."eth0"."100" = INTEGER: 244269 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutPps."eth0"."100" = INTEGER: 8754 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBytes."eth0"."100" = INTEGER: 139077237 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutDrops."eth0"."100" = INTEGER: 35 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutKind."eth0"."100" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBps."eth0"."100" = INTEGER: 9132541 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutOverlimits."eth0"."100" = INTEGER: 7904 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: 93768 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassPackets."eth0"."100".2 = INTEGER: 150501 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".1 = INTEGER: 6307514 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".2 = INTEGER: 132769723 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: 4154 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPackets."eth0"."100" = INTEGER: 1060397 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPps."eth0"."100" = INTEGER: 19584 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBytes."eth0"."100" = INTEGER: 1592679143 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInDrops."eth0"."100" = INTEGER: 5563 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInKind."eth0"."100" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBps."eth0"."100" = INTEGER: 28777589 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.672 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.672/0.672/0.672/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 44542 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 131 MBytes 1.10 Gbits/sec 456 60.8 KBytes [ 5] 1.00-2.00 sec 150 MBytes 1.26 Gbits/sec 587 26.9 KBytes [ 5] 2.00-3.00 sec 139 MBytes 1.16 Gbits/sec 491 18.4 KBytes [ 5] 3.00-4.00 sec 83.9 MBytes 704 Mbits/sec 299 50.9 KBytes [ 5] 4.00-5.00 sec 137 MBytes 1.15 Gbits/sec 498 41.0 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 640 MBytes 1.07 Gbits/sec 2331 sender [ 5] 0.00-5.00 sec 639 MBytes 1.07 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 40482 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 85.3 MBytes 715 Mbits/sec 290 12.7 KBytes [ 5] 1.00-2.00 sec 102 MBytes 855 Mbits/sec 377 21.2 KBytes [ 5] 2.00-3.00 sec 132 MBytes 1.11 Gbits/sec 480 31.1 KBytes [ 5] 3.00-4.00 sec 147 MBytes 1.24 Gbits/sec 545 33.9 KBytes [ 5] 4.00-5.00 sec 158 MBytes 1.32 Gbits/sec 605 36.8 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 624 MBytes 1.05 Gbits/sec 2297 sender [ 5] 0.00-5.00 sec 624 MBytes 1.05 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 58024 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 190 66.5 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 93.8 Mbits/sec 83 67.9 KBytes [ 5] 2.00-3.00 sec 11.7 MBytes 98.5 Mbits/sec 62 83.4 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 93.8 Mbits/sec 73 86.3 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 93.8 Mbits/sec 97 49.5 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.5 MBytes 99.9 Mbits/sec 505 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 36110 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 160 87.7 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 94.4 Mbits/sec 71 91.9 KBytes [ 5] 2.00-3.00 sec 11.7 MBytes 98.5 Mbits/sec 67 91.9 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 93.8 Mbits/sec 73 93.3 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 94.3 Mbits/sec 57 93.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.6 MBytes 100 Mbits/sec 428 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::telOSDxMonDBInterfacesBridgeTrafficControlOutPackets."br0" = INTEGER: 233547 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutPps."br0" = INTEGER: 8824 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBytes."br0" = INTEGER: 138331114 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: 9272763 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutOverlimits."br0" = INTEGER: 7891 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: 75536 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassPackets."br0".2 = INTEGER: 158011 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".1 = INTEGER: 5074181 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".2 = INTEGER: 133256933 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: 4149 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPackets."br0" = INTEGER: 923276 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPps."br0" = INTEGER: 17936 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBytes."br0" = INTEGER: 1385507384 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInDrops."br0" = INTEGER: 4666 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInKind."br0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBps."br0" = INTEGER: 26268924 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.572 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.572/0.572/0.572/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 36636 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 184 MBytes 1.54 Gbits/sec 668 58.0 KBytes [ 5] 1.00-2.00 sec 191 MBytes 1.60 Gbits/sec 668 39.6 KBytes [ 5] 2.00-3.00 sec 185 MBytes 1.56 Gbits/sec 673 41.0 KBytes [ 5] 3.00-4.00 sec 199 MBytes 1.67 Gbits/sec 721 31.1 KBytes [ 5] 4.00-5.00 sec 180 MBytes 1.51 Gbits/sec 622 18.4 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 939 MBytes 1.58 Gbits/sec 3352 sender [ 5] 0.00-5.00 sec 939 MBytes 1.57 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 38056 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 163 MBytes 1.37 Gbits/sec 569 17.0 KBytes [ 5] 1.00-2.00 sec 135 MBytes 1.13 Gbits/sec 513 48.1 KBytes [ 5] 2.00-3.00 sec 134 MBytes 1.13 Gbits/sec 532 26.9 KBytes [ 5] 3.00-4.00 sec 143 MBytes 1.20 Gbits/sec 512 50.9 KBytes [ 5] 4.00-5.00 sec 110 MBytes 925 Mbits/sec 406 28.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 686 MBytes 1.15 Gbits/sec 2532 sender [ 5] 0.00-5.00 sec 685 MBytes 1.15 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 57738 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 144 97.6 KBytes [ 5] 1.00-2.00 sec 11.7 MBytes 98.5 Mbits/sec 101 66.5 KBytes [ 5] 2.00-3.00 sec 11.4 MBytes 95.1 Mbits/sec 77 77.8 KBytes [ 5] 3.00-4.00 sec 11.4 MBytes 95.7 Mbits/sec 76 83.4 KBytes [ 5] 4.00-5.00 sec 11.4 MBytes 95.4 Mbits/sec 67 86.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.6 MBytes 100 Mbits/sec 465 sender [ 5] 0.00-5.00 sec 58.4 MBytes 98.0 Mbits/sec receiver iperf Done.
Step 7: Initiate a bandwidth test from DUT0 to DUT1
admin@DUT1$ monitor test performance server port 4321 admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 4321 parallel 1Expect the following output on
DUT0:Connecting to host 192.168.100.2, port 4321 [ 5] local 192.168.100.1 port 40112 connected to 192.168.100.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.3 MBytes 120 Mbits/sec 171 89.1 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 93.9 Mbits/sec 66 90.5 KBytes [ 5] 2.00-3.00 sec 11.2 MBytes 93.8 Mbits/sec 83 86.3 KBytes [ 5] 3.00-4.00 sec 11.9 MBytes 100 Mbits/sec 78 79.2 KBytes [ 5] 4.00-5.00 sec 11.3 MBytes 94.8 Mbits/sec 75 80.6 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.9 MBytes 100 Mbits/sec 473 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::telOSDxMonDBInterfacesBridgeVifTrafficControlOutPackets."br0"."100" = INTEGER: 269573 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutPps."br0"."100" = INTEGER: 9013 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBytes."br0"."100" = INTEGER: 140738841 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutDrops."br0"."100" = INTEGER: 34 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutKind."br0"."100" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBps."br0"."100" = INTEGER: 9183057 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutOverlimits."br0"."100" = INTEGER: 7747 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: 111694 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassPackets."br0"."100".2 = INTEGER: 157879 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".1 = INTEGER: 7494070 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".2 = INTEGER: 133244771 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: 4074 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPackets."br0"."100" = INTEGER: 1184055 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPps."br0"."100" = INTEGER: 20620 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBytes."br0"."100" = INTEGER: 1780546251 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInDrops."br0"."100" = INTEGER: 5932 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInKind."br0"."100" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBps."br0"."100" = INTEGER: 30376811 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.376 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.376/0.376/0.376/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 51322 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 185 MBytes 1.56 Gbits/sec 597 31.1 KBytes [ 5] 1.00-2.00 sec 144 MBytes 1.21 Gbits/sec 523 38.2 KBytes [ 5] 2.00-3.00 sec 174 MBytes 1.46 Gbits/sec 636 28.3 KBytes [ 5] 3.00-4.00 sec 171 MBytes 1.43 Gbits/sec 603 18.4 KBytes [ 5] 4.00-5.00 sec 174 MBytes 1.46 Gbits/sec 631 25.5 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 849 MBytes 1.42 Gbits/sec 2990 sender [ 5] 0.00-5.00 sec 848 MBytes 1.42 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 53268 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 181 MBytes 1.52 Gbits/sec 677 22.6 KBytes [ 5] 1.00-2.00 sec 104 MBytes 871 Mbits/sec 386 15.6 KBytes [ 5] 2.00-3.00 sec 132 MBytes 1.11 Gbits/sec 471 28.3 KBytes [ 5] 3.00-4.00 sec 132 MBytes 1.10 Gbits/sec 491 39.6 KBytes [ 5] 4.00-5.00 sec 118 MBytes 989 Mbits/sec 413 25.5 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 666 MBytes 1.12 Gbits/sec 2438 sender [ 5] 0.00-5.00 sec 665 MBytes 1.12 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 35270 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 143 70.7 KBytes [ 5] 1.00-2.00 sec 11.3 MBytes 94.9 Mbits/sec 80 77.8 KBytes [ 5] 2.00-3.00 sec 11.7 MBytes 98.5 Mbits/sec 65 80.6 KBytes [ 5] 3.00-4.00 sec 11.4 MBytes 95.4 Mbits/sec 71 87.7 KBytes [ 5] 4.00-5.00 sec 11.3 MBytes 94.9 Mbits/sec 59 91.9 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.5 MBytes 99.8 Mbits/sec 418 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 56740 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 153 84.8 KBytes [ 5] 1.00-2.00 sec 11.5 MBytes 96.4 Mbits/sec 63 73.5 KBytes [ 5] 2.00-3.00 sec 11.4 MBytes 95.9 Mbits/sec 77 74.9 KBytes [ 5] 3.00-4.00 sec 10.9 MBytes 91.7 Mbits/sec 68 79.2 KBytes [ 5] 4.00-5.00 sec 11.5 MBytes 96.4 Mbits/sec 74 77.8 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.4 MBytes 99.7 Mbits/sec 435 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: 0Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPackets."bond0" = INTEGER: 269086 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPps."bond0" = INTEGER: 9152 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBytes."bond0" = INTEGER: 140717134 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutDrops."bond0" = INTEGER: 34 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutKind."bond0" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBps."bond0" = INTEGER: 9177952 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutOverlimits."bond0" = INTEGER: 7872 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: 106040 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassPackets."bond0".2 = INTEGER: 163046 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".1 = INTEGER: 7112078 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".2 = INTEGER: 133605056 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: 4137 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPackets."bond0" = INTEGER: 1105018 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPps."bond0" = INTEGER: 20212 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBytes."bond0" = INTEGER: 1659924277 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInDrops."bond0" = INTEGER: 5476 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInKind."bond0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBps."bond0" = INTEGER: 29737747 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.540 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.540/0.540/0.540/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 44832 connected to 10.0.0.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 101 MBytes 850 Mbits/sec 362 20.9 KBytes [ 5] 1.00-2.00 sec 77.7 MBytes 652 Mbits/sec 290 45.9 KBytes [ 5] 2.00-3.00 sec 120 MBytes 1.01 Gbits/sec 462 30.6 KBytes [ 5] 3.00-4.00 sec 152 MBytes 1.27 Gbits/sec 574 30.6 KBytes [ 5] 4.00-5.00 sec 150 MBytes 1.25 Gbits/sec 540 43.1 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 600 MBytes 1.01 Gbits/sec 2228 sender [ 5] 0.00-5.01 sec 600 MBytes 1.00 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 41136 connected to 10.0.0.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 173 MBytes 1.45 Gbits/sec 639 29.2 KBytes [ 5] 1.00-2.00 sec 136 MBytes 1.14 Gbits/sec 498 29.2 KBytes [ 5] 2.00-3.00 sec 89.3 MBytes 749 Mbits/sec 312 30.6 KBytes [ 5] 3.00-4.00 sec 120 MBytes 1.01 Gbits/sec 475 13.9 KBytes [ 5] 4.00-5.00 sec 151 MBytes 1.27 Gbits/sec 581 37.5 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 669 MBytes 1.12 Gbits/sec 2505 sender [ 5] 0.00-5.00 sec 668 MBytes 1.12 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 47248 connected to 10.0.0.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 13.9 MBytes 117 Mbits/sec 154 90.4 KBytes [ 5] 1.00-2.00 sec 11.9 MBytes 99.5 Mbits/sec 65 93.2 KBytes [ 5] 2.00-3.00 sec 11.3 MBytes 94.8 Mbits/sec 85 97.3 KBytes [ 5] 3.00-4.00 sec 11.4 MBytes 95.4 Mbits/sec 78 91.8 KBytes [ 5] 4.00-5.00 sec 11.6 MBytes 96.9 Mbits/sec 64 94.6 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 60.0 MBytes 101 Mbits/sec 446 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 44910 connected to 10.0.0.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.6 MBytes 122 Mbits/sec 185 104 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 94.3 Mbits/sec 95 72.3 KBytes [ 5] 2.00-3.00 sec 11.5 MBytes 96.4 Mbits/sec 72 75.1 KBytes [ 5] 3.00-4.00 sec 11.9 MBytes 100 Mbits/sec 68 79.3 KBytes [ 5] 4.00-5.00 sec 11.4 MBytes 95.4 Mbits/sec 81 65.4 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 60.6 MBytes 102 Mbits/sec 501 sender [ 5] 0.00-5.00 sec 58.9 MBytes 98.8 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: 234370 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutPps."tun0" = INTEGER: 8320 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBytes."tun0" = INTEGER: 136187322 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutDrops."tun0" = INTEGER: 35 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutKind."tun0" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBps."tun0" = INTEGER: 8808589 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutOverlimits."tun0" = INTEGER: 7626 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: 70085 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassPackets."tun0".2 = INTEGER: 164285 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".1 = INTEGER: 3728094 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".2 = INTEGER: 132459228 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: 4012 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPackets."tun0" = INTEGER: 942940 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPps."tun0" = INTEGER: 16049 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBytes."tun0" = INTEGER: 1378987779 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInDrops."tun0" = INTEGER: 4777 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInKind."tun0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBps."tun0" = INTEGER: 22855872 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInOverlimits."tun0" = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInRate."tun0" = INTEGER: 0